> 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/access-and-sharing/overview/test-access.md).

# Test access before publishing

Use representative accounts to verify the access policy, including actions that must fail.

**Before you start:** use synthetic test records, identify the app environment and version, and write the expected result for each role.

## Test matrix

| Test                                 | What to verify                                              |
| ------------------------------------ | ----------------------------------------------------------- |
| Sign-in with intended account        | Identity and membership are correct.                        |
| Sign-in with unintended account      | Access follows the intended rejection or onboarding policy. |
| Allowed page and record              | Intended content is available.                              |
| Restricted page or direct record URL | Unauthorized content is unavailable.                        |
| Allowed create/update                | Only the intended test record changes.                      |
| Denied create/update/delete          | Request fails and data remains unchanged.                   |
| Search, export, and related records  | No data outside the permitted scope.                        |
| Workflow or API action               | The same identity and record restrictions apply.            |
| User with missing access property    | The defined restricted behavior occurs.                     |
| Membership or role change            | A fresh sign-in and existing session behave as intended.    |

## Run and record

1. Use [invited-user preview](/ai-app-builder/preview-and-troubleshoot/preview-as-an-invited-user.md) to inspect pages and controls.
2. Sign in separately as each test user to verify authentication and published-app behavior.
3. Exercise allowed and denied operations on test data.
4. Check the resulting records and available logs.
5. Record expected result, actual result, and evidence for each case.
6. Fix failures and repeat the affected tests before release.

For multi-customer apps, run [the two-customer isolation test](/access-and-sharing/app-and-data-permissions/customer-data-isolation.md). For action behavior, see [the AI App Builder action testing guide](/ai-app-builder/test-and-publish/check-data-actions-and-user-access.md).


---

# 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/access-and-sharing/overview/test-access.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.