> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcdemo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Publish and share

> Make a reviewed version available and choose how people can open it.

Your editor contains the working draft. **Publish** creates the version shown to viewers. Later edits stay in the draft until you publish again, so you can prepare changes without updating the live experience midway through a review.

1. Preview the complete flow and check its captured content.
2. Select **Publish** in the editor and follow any prompts to review pending work.
3. Open **Share**, choose the access level, then copy a link or [embed](https://docs.arcdemo.io/share/embed.md).
4. Open the published result as a viewer and check the first step, navigation, and ending.

When the editor shows **Unpublished changes**, publish again to update the live version. If publishing fails, the editor displays an error; resolve it and retry. A failed first publish leaves the demo private.

## Choose who can open the demo

In **Share**, review the access setting before sending a link:

| Access | How viewers open it |
| - | - |
| Private | Through the individual share links you create. Each link can be tracked and revoked. |
| Unlisted | Anyone with the plain link can open it, subject to the demo's link restrictions. |
| Public | Anyone with the plain link can open it, even when other links have restrictions. |

A private share link is still access for anyone who receives it; it is not the same as requiring a workspace login. Treat the URL as something you control and use a password, expiry, or view limit when appropriate. Available controls can depend on your plan.

## Create a link for an audience

Use a named link when you want to distinguish a campaign or recipient. In the Link tab, you can set a label and, where available, a password, expiry, or view limit. Review the link settings before copying it. Deleting a link stops it working for people who received that link.

For example, create one link for a sales follow-up and another for a website campaign. Give each a name your team will recognize, configure only the restrictions that fit its audience, and test each link in a separate browser session. A password for a share link must be 12–128 characters. An expiry or view limit stops that link opening when the limit is reached; it does not change other links to the demo.

## Change or withdraw access

Use the link's controls to edit its settings, disable it temporarily, or delete it. Before disabling or deleting a link, check whether it is used by an embed or follow-up that should continue working. Test the affected destination after the change.

Restrictions on one link do not protect an unrestricted plain URL. In particular, **Public** permits the plain link even if another link has restrictions. If the experience is intended only for recipients of controlled links, choose **Private**, review every active link, and test the plain URL and each intended link as an outside viewer. A link can be forwarded, so choose its restrictions with that possibility in mind.

If you need to remove the live demo altogether, use the editor's **Take demo offline** action. This stops its public viewer link while keeping the draft and published version history.

## Schedule availability

In the editor's **Manage** view, open **Scheduling** to set an **Auto-publish** time or an **Auto-unpublish** time. The date and time fields use your browser's local time. If both are set, auto-unpublish must be later than auto-publish.

For a planned launch, set and save the auto-publish time, then publish the reviewed draft to stage its snapshot. The demo remains unavailable to public viewers until the scheduled time. Setting a future auto-publish time on an already published demo also makes its public playback unavailable until that time, so do not use this to quietly prepare an update to a demo that must stay online.

Auto-unpublish takes the demo offline at the selected time across its plain URL, share links, and embeds. This is different from expiring a single share link. Clear a schedule when it is no longer intended, and check the displayed time before relying on it. After the planned change, test the actual link and any embeds; coordinate with the owners of pages that depend on them.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.