> 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/start-here.md).

# Access & Governance overview

Set up who can enter your app, what each person can do, and how you verify access before sharing it.

## Start with one complete access flow

1. Choose a [built-in role](/access-and-sharing/teams-and-roles/built-in-roles.md) for an intended user.
2. [Invite that user by email](/access-and-sharing/members-users-and-groups/invite-by-email.md) and confirm their team.
3. Configure [authentication](/access-and-sharing/authentication-and-sso.md) for the audience.
4. Review [page, action, and data permissions](/access-and-sharing/app-and-data-permissions.md).
5. [Test allowed and denied actions](/access-and-sharing/overview/test-access.md) before publishing.
6. Use the [audit trail](/access-and-sharing/audit-logs-privacy-and-security/review-the-audit-trail.md) and [system logs](/access-and-sharing/audit-logs-privacy-and-security/investigate-system-logs.md) to investigate unexpected behavior.

## Find the right guide

| Section                                                                               | What you will accomplish                                             |
| ------------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
| [Users and invitations](/access-and-sharing/members-users-and-groups.md)              | Invite people, manage membership, and import or export user records. |
| [Teams and roles](/access-and-sharing/teams-and-roles.md)                             | Choose built-in roles and organize people into teams.                |
| [Authentication and SSO](/access-and-sharing/authentication-and-sso.md)               | Choose and troubleshoot a sign-in method.                            |
| [App and data permissions](/access-and-sharing/app-and-data-permissions.md)           | Define access to pages, actions, and records.                        |
| [Test and govern access](/access-and-sharing/overview.md)                             | Review AI-generated changes and verify each user experience.         |
| [Audit trail and system logs](/access-and-sharing/audit-logs-privacy-and-security.md) | Find activity and diagnose errors.                                   |
| [Security and data handling](/access-and-sharing/data-privacy-and-security.md)        | Understand storage, credentials, and recovery responsibilities.      |

## Four concepts to keep separate

**Authentication** establishes identity. **Membership and teams** associate people with the app. **Authorization** determines permitted actions and records. **Publishing** makes an app version available to its audience.

A successful sign-in does not prove that a user has the right permissions. A successful preview does not prove that a record-level restriction is enforced.

The written guides use the current Users and More navigation. Older provider tutorials and Classic builder examples are labeled where their screens differ.


---

# 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/start-here.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.