> 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/verify-a-release.md).

# Verify a published release

Check the released app at the address users will actually open. Passing a Preview test is useful, but does not replace this check.

**Before you start:** record the app, environment, reviewed version, published address, and release time. Prepare synthetic records and representative user accounts.

## Run the checks

| Check                                  | Expected result                                       |
| -------------------------------------- | ----------------------------------------------------- |
| Open the published address             | The intended app loads over the expected connection.  |
| Sign in as an intended user            | The correct identity and permitted pages appear.      |
| Find a known reviewed change           | The released behavior matches the approved version.   |
| Read a permitted record                | The expected data is available.                       |
| Run a permitted test write             | Only the intended source record changes.              |
| Attempt a restricted action            | The request is denied and the data remains unchanged. |
| Test a second customer or role         | No data outside that user's scope is exposed.         |
| Open the app on supported screen sizes | Navigation and essential actions remain usable.       |

## Record the outcome

For each important task, record expected result, actual result, and evidence. Include the identity and environment so another reviewer can reproduce the test.

If a check fails, identify whether it concerns [the released version](/jet-bridge-deployment/logs-and-troubleshooting/published-changes-missing.md), [access](/jet-bridge-deployment/logs-and-troubleshooting/published-app-access-fails.md), or [a resource or deployment service](/jet-bridge-deployment/logs-and-troubleshooting/resource-and-deployment-errors.md). Compare with [Version History](/ai-app-builder/test-and-publish/version-history.md) before deciding whether to correct the app or revert a change.

Repeat the affected checks after a correction or revert. Review separately whether any failed action changed data or triggered an external operation.


---

# 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/verify-a-release.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.