# Publish, share, and embed

Publish a saved Page revision, choose public or administrator-only access, embed on allowed websites, and manage history.

## Review before publishing

Choose **Save draft**, then **Check for issues**. Follow suggestions to the affected widgets and review your text, mappings, images, links, and actions. Open **Private preview** to inspect the saved draft. Review Phone, Tablet, and Desktop layouts.

Preview suppresses workflow execution and Line launches. It helps you review the design; it does not verify external delivery. Remove **FileUpload** before publishing because public guest uploads are unavailable.

## Choose who can open the Page

In **My Pages**, open the Page’s **Publication** action, or choose **Publishing and embedding** in Studio. Review the current visibility before the first publication.

| Visibility | Who can use it | Sharing |
| --- | --- | --- |
| **Public · Anyone with the published link** | Visitors with the published link. | Published URL and allowed website embeds. |
| **Private · Organization administrators only** | Authorized administrators in the current organization. | Authenticated private links. Cross-site embeds are unavailable. |

Choose **Change visibility to private** before first publication if the Page must never be public. **Change visibility to public** makes its published content available to visitors, so review every field and action first.

Private publication is not a customer login portal or a promise of access for all organization Members. Both public and private publications consume a published-Page slot.

## Publish a saved revision

Choose **Publish saved draft**. Publication explicitly selects what visitors see. Later draft edits and Auto Save do not change the published version until you publish again.

For a public Page, use **Open published Page** and share the URL supplied by Chatigram. For a private Page, use **View inside Chatigram** or the available standalone private link, while signed in with the authorized organization administrator account. Use the generated links rather than constructing a Page address yourself.

Test with synthetic information and an appropriate test workflow before inviting real visitors. Verify the receipt text and the workflow result separately. Review the complete [plan comparison](/workspace/billing/) if publication is blocked by an allowance.

## Embed on your website

Public Pages support **Inline embed** and **Popup embed** code in **Publishing and embedding**.

1. Enter each permitted website in **Websites allowed to embed this Page (one HTTPS origin per line)**.
2. Use the origin only: scheme and hostname, plus a non-default port if needed. For example, `https://www.example.com`; do not include a page path.
3. Apply the allowed website settings, then copy the desired embed code to your website.
4. Test on the exact allowed hostname. An apex domain and its `www` hostname are different origins.
5. If the Page contains Live Chat, check that the Line also allows the host website.

Use a descriptive iframe title. Check the embedded height, keyboard access, and narrow-screen layout. For a popup, make opening and closing clear and verify that keyboard users can return to the website. Private Pages cannot be embedded on another website.

## Restore or withdraw a publication

**Publication history** lists published revisions. **Restore publication** selects an earlier published version for visitors. Review its connected resources and actions before restoring it.

**Draft history** restores editable work and requires another publish to change what visitors see. Keep the distinction clear when recovering from an unwanted edit.

Choose **Unpublish** to withdraw visitor access and free the publication slot. Check the old link and embedded version after withdrawing a Page. Draft content remains available for further editing.

## Keep data and actions trustworthy

Publish only intended database columns and public-safe feed content. A widget hidden by Conditions still has its content in the public definition. A URL parameter, tracking reference, or hidden field does not establish a visitor’s identity.

An open Page may retain inputs during a temporary interruption, but refresh does not preserve form answers, tracking results, or pending action identifiers. Avoid promising cross-device recovery. If a visitor is unsure whether a request arrived, check the workflow outcome before asking them to repeat a consequential action.
