22 Share a character and submit it for review

Review scope: Linked public documentation checked October 30, 2026. Examples are proposed checks, not recorded OD results; use your account's current controls.

Tutorial index

You will choose an appropriate visibility setting, prepare a readable public introduction, and understand submission and rejection handling. The example is Mira, a 30-year-old adult archivist in an original fictional archive. Reading this tutorial does not publish anything.

Choose the audience first

Private is the development setting. Unlisted is used for direct-link testing. Public requests inclusion in the reviewed community catalog. A link-sharing setting is not a claim that the content is secret or encrypted. The publishing guide recommends testing before submission, and meeting length requirements alone does not guarantee approval. Publishing guide

You need a signed-in creator account, a saved character, and access to its editor. The hosted FAQ states that Public submissions require Premium. At the actual submission step, follow the current account requirement and field validation rather than treating remembered character counts as universal limits. Sharing FAQ

Prepare Mira for another reader

1. Save a copy of the current character text before changing it. Test that the portrait, description, greeting, scenario, and personality all describe the same person and premise.
2. Open My AI, choose Mira, open the three-dot menu, then select Edit. Find the visibility setting actually offered there.
3. Keep development work Private. Choose Unlisted when you deliberately want direct-link testing. To share through the documented route, open the character's chat and copy its URL. Inspect its preview before sending it; the FAQ distinguishes a character-image preview from a generic banner. A preview is only a preliminary check: open the exact link in a separate browser session with the intended access, complete any ordinary sign-in or age steps, and verify the destination character. Sharing a character link is not a demonstrated export of your private conversation. Sharing instructions
4. Ask a tester to begin from the description and greeting without supplying your private author notes. Record where they cannot understand their role or where the character contradicts the premise.

Here is an original example for Public Description:

Mira, 30, is the archivist of a small riverside archive. She is patient,
precise, and quietly amused by visitors who arrive with impossible questions.
Today a sealed parcel awaits dispatch, but its address card names two different
streets. You are a visitor at the desk, free to investigate records, ask about it,
or pursue your own reason for coming. Mira can explain the catalog, but she
will not decide your next action. The story begins inside the archive.

This describes what another person can expect. This parcel premise is an alternative to the earlier missing-map opening: use it only after reconciling the Scenario and Greeting with that premise. The writing guide describes Public Description as discovery copy, not a field used by the chat model. Put story-relevant answers and operational rules in the appropriate AI-facing fields; do not treat those fields as secure storage for real secrets. Check the current validator after entering your own version.

Audit each promise in the description. If you advertise a mystery, progression system, custom commands, or a particular interaction, verify that the character and offered controls actually support it. A command invented in a source document is creator-authored text until implemented and tested; the public introduction cannot install it.

Submit and inspect the result

After the final text edits, the publishing guide, last modified July 27 and re-read November 1, 2026, recommends regenerating so the latest changes are saved before submission. Follow the current completion flow, read the displayed charge before any generation, and reopen the saved fields and preview to confirm the intended revision. A successful text save alone is not proof that the final publication preview includes it.

5. Review the current content requirements, including both the writing and profile image. Original names alone are insufficient if the design still reproduces a recognizable existing character or real person's likeness. Content review
6. When the tested version is ready, choose Public and use the actual submission flow. Confirm that the intended version and display image are selected. Read any validation messages before submitting.
7. Check the resulting status. Submitted, awaiting review, and approved are different outcomes. Do not assume that a saved edit or copied link means catalog approval.

If rejected, keep the exact reason, identify the affected field or image, correct the cause across the character, test privately, and then resubmit. Use the current appeal route when you believe a rule was applied incorrectly. Revision and appeal guidance

Three common problems

• The link opens a generic page: recheck the chosen visibility, character URL, and preview. Do not repeatedly send a link you have not inspected.
• The form reports insufficient or inconsistent information: follow that field's current validator; improve the scenario or writing rather than adding meaningless padding.
• A submission remains pending or is rejected: inspect its recorded status and reason. Avoid duplicate submissions while waiting, and do not promise a fixed approval time.

Comic publication and selling a media pack are separate actions from publishing a character. Do not activate those flows merely because you changed this character's visibility.