> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/jet-bridge-deployment/publish-your-app.md).

# Publish your app

Publish after the reviewed app, data connections, and permissions match the intended use.

## Before publishing

* Confirm the target [environment](/jet-bridge-deployment/environments.md) and resources.
* Complete [data and access tests](/ai-app-builder/test-and-publish/check-data-actions-and-user-access.md) with synthetic records.
* Check [Desktop, Tablet, and Mobile](/ai-app-builder/preview-and-troubleshoot/control-app-preview.md) layouts.
* [Preview as an invited user](/ai-app-builder/preview-and-troubleshoot/preview-as-an-invited-user.md) and resolve relevant errors.
* Record the reviewed [app version](/ai-app-builder/test-and-publish/version-history.md) and recovery approach.

## Publish the reviewed changes

1. Open the intended app and environment.
2. Review the result of the last generated or manual change.
3. Select **Publish** in the top toolbar.
4. Follow any publishing options or confirmation shown for your app.
5. Open the published app at its configured address.
6. [Verify the release](/jet-bridge-deployment/publish-your-app/verify-a-release.md) with an intended test user.

![Builder toolbar with separate Share, Version History, and Publish controls](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FaoHXIlvOavCeV3oYtmyE%2Fpublish-toolbar.png?alt=media)

![Expanded Publish menu showing the pending change count and Open published App](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FIPTzOKlYhgvNDHCQBE9V%2Fai-publish-options.jpg?alt=media)

The expanded menu separates publishing pending changes from opening the published app.

Non-builder users see the published app. A change that appears in Preview may still be unpublished.

For the AI builder's full walkthrough, see [Preview and publish an AI app](/ai-app-builder/test-and-publish/preview-and-publish-an-ai-app.md). For an existing Classic app, see [Classic Preview & Publish](/classic-app-builder/preview-and-publish.md).

## If the result differs from Preview

Start with [Published changes are missing](/jet-bridge-deployment/logs-and-troubleshooting/published-changes-missing.md). Check the environment, address, and publication result before making another app change. Publishing and inviting a user are separate actions; use [Share with the intended audience](/jet-bridge-deployment/share-and-embed/share-your-app.md) when access is the next step.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/jet-bridge-deployment/publish-your-app.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.