> 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/members-users-and-groups/security-and-privacy.md).

# Manage members and access

In  this section you will learn about Users and Permissions

Use the Users list to review who belongs to the app and the team associated with each person.

## Review a user

1. Open **Users** in the builder navigation, then the **Users** tab.
2. Search for the person's email or name.
3. Review their team and any properties used by access rules.
4. Compare the assignment with the [built-in role descriptions](/access-and-sharing/teams-and-roles/built-in-roles.md).
5. Test the resulting experience with the [invited-user preview](/ai-app-builder/preview-and-troubleshoot/preview-as-an-invited-user.md) and, for sign-in checks, the person's test account.

## Change access deliberately

When changing membership through the controls available in your app, record the intended outcome first: builder access, app editing, or viewing only. Check all relevant team assignments; do not infer combined permissions from one team name.

For someone who leaves your organization, review app membership, identity-provider access, shared invitation links, and any separately issued credentials. Changing a property such as Status to Inactive is not by itself proof that sign-in or data access has been revoked.

After a change, check both a fresh sign-in and any existing session. Record the observed behavior instead of assuming immediate session termination.

## If the user sees the wrong app

Confirm the app and environment, published version, signed-in account, and team assignment. Use [sign-in troubleshooting](/access-and-sharing/authentication-and-sso/troubleshoot-sign-in.md) for login failures and [access tests](/access-and-sharing/overview/test-access.md) for permission failures.

For new people, continue with [email invitations](/access-and-sharing/members-users-and-groups/invite-by-email.md) or [invitation links](/access-and-sharing/members-users-and-groups/invite-with-a-link.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/members-users-and-groups/security-and-privacy.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.