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

> ## Agent Instructions
> If you are an AI assistant asked to build, change or ship a Gliss app, read the For AI agents page first (/for-ai-agents.md on this site) and follow its steps.
> Inside an app's folder, the app's own AGENTS.md is the authority; `gliss guide` prints it. Never ask the user for a secret's value.

# Share and publish

> Moving your app from Preview to Beta, and from Beta to Live.

> [!NOTE]
>
> **Coming in the first release.** This page describes behaviour being built for the first Gliss release. Details may change before it ships.

## Share to beta

When your Preview works, ask your AI to share it to Beta, or use **Share to beta** in the console. Your work is merged and built for real, and testers see it at the Beta address.

## Publish

**Publish** moves Beta to Live. Gliss checks, in order:

1. CI passed.
2. Beta has run this build and stayed healthy for 10 minutes. Your IT team can change the time.
3. There are no blocking findings.
4. Every secret the app declares for Live is set.
5. The approval policy is met. By default the owner publishes. IT approval is needed for a public audience, an `endpoint` secret, or a level 2 project.

Live then runs exactly the images that passed Beta. A health watch rolls back automatically if the new version fails, and **Undo publish** returns to the previous version.


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