Publishing & Sharing
Publish an app version to make it runnable, then control who in your organization can run or edit it.
A draft app only exists for you, in the builder. To let people actually use it, you publish a version and share it.
Draft vs. Live
Every app has a status, shown on its gallery card:
- Draft — no published version yet. The app can only be opened in the builder; there's nothing to run.
- Live — a version has been published. The app runs when opened, and can be shared.
Publishing takes a snapshot of the current build as a version. You can keep building afterward — your new changes stay in the draft until you publish again, so the Live app your team uses never changes underneath them mid-task.
Sharing an app
Open a Live app and you'll find the owner actions, including Share. The share dialog gives you two ways to grant access:
- Make it visible to your organization — turn on org visibility so everyone in your workspace can find and run the app.
- Invite specific people — search for teammates and add them individually, each with a role.
Roles
When you share an app with someone, you choose what they can do:
| Role | Can run the app | Can edit in the builder |
|---|---|---|
| User | ✓ | — |
| Builder | ✓ | ✓ |
Use User for people who just need to run the tool, and Builder for collaborators who help you develop it.
You remain the owner of an app you created. Owner-only actions — publishing, sharing, the activity log, and the confirmation policy — are always enforced on the server, not just hidden in the UI.
The confirmation policy
Owner actions include a confirm destructive actions toggle. When it's on, the app pauses for an explicit confirmation before it runs anything potentially destructive. Leave it on for tools that can change or delete data, and turn it off only for read-only apps where the extra click is just friction.
Activity
The Activity panel in the owner actions shows what the app has been doing — a running log you can open any time to see how it's being used.