> 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.md).

# Test and govern access

Review access as part of every release that changes users, authentication, pages, data queries, or workflows.

## Before publishing

1. Write the intended access for each audience.
2. [Review AI-generated changes](/access-and-sharing/overview/review-ai-changes.md) that affect data or authorization.
3. Use [Preview as an invited user](/ai-app-builder/preview-and-troubleshoot/preview-as-an-invited-user.md) to inspect the app from that user's perspective.
4. Run [allowed and denied access tests](/access-and-sharing/overview/test-access.md).
5. Record the app version, environment, identities tested, and results.

Preview helps reveal differences in the interface. Use actual test sign-ins and data requests to check authentication and enforcement.

## Keep ownership clear

Assign an owner for membership reviews, authentication configuration, permission rules, and incident investigation. Recheck access when a person changes responsibilities or leaves, and after changing team or user properties used by rules.

Use [the audit trail](/access-and-sharing/audit-logs-privacy-and-security/review-the-audit-trail.md) to review available activity and [system logs](/access-and-sharing/audit-logs-privacy-and-security/investigate-system-logs.md) to investigate errors. Confirm event coverage and retention for your requirements rather than assuming the logs form a complete compliance record.

## Review the app version

Use [Version History](/ai-app-builder/test-and-publish/version-history.md) to identify the app state being reviewed. Inspect changes before reverting, record the selected version in your review, and repeat permission tests after a revert. Check database records separately: app version history is not a record-level data backup.


---

# 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.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.