> 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/ai-app-builder/test-and-publish/preview-and-publish-an-ai-app.md).

# Preview and publish an AI app

Publish the app after checking its pages, data actions, and user access.

## Before publishing

Complete [data and access tests](/ai-app-builder/test-and-publish/check-data-actions-and-user-access.md). Inspect [Desktop, Tablet, and Mobile](/ai-app-builder/preview-and-troubleshoot/control-app-preview.md) and confirm the app works for an invited user. Resolve relevant Console errors.

## Publish

1. Open the project and environment you intend to release.
2. Review the app after the last generated or manual change.
3. Click **Publish** in the builder's top toolbar.
4. Review the publishing options shown for your project and complete the publish flow.
5. Open the published app at its configured address.

For environment configuration, domains, and deployment choices, follow [Publish & Deploy](/jet-bridge-deployment/overview.md).

![Publish menu showing pending changes, Publish, the published app address, and Connect Custom domain](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)

Review the pending changes before confirming Publish. Use Open published App to check the released version.

## Check the published app

Sign in as a representative user. Open the critical pages and repeat the main task with test records. Verify the source result of a write action and check a restricted user is still denied.

A successful Preview check is useful evidence, but the published app must also be checked with its actual configuration.

## If publication or verification fails

Capture the error, environment, app URL, and time. Determine whether the problem is publishing, loading, data access, or an action before changing the app.

Use [Console and logs](/ai-app-builder/preview-and-troubleshoot/inspect-app-console-and-logs.md) for Preview diagnostics and [troubleshooting](/ai-app-builder/preview-and-troubleshoot/troubleshoot-the-prompt-assistant.md) for a failed generation or revision.


---

# 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/ai-app-builder/test-and-publish/preview-and-publish-an-ai-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.