> 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/faq-and-troubleshooting/403-and-user-permission-errors.md).

# A user gets 403 or cannot access a page

A 403 or access-denied message means you need to check the affected user's access to the particular app, page, or action.

## Check the affected account and role

1. Confirm the user is signing in to the intended app and environment with the expected email address.
2. Ask an administrator to compare the user's assigned groups, page access, and data/action permissions with the intended role.
3. Save any work, sign out, and sign in again. A fresh session can help when permissions have changed; it does not repair an incorrect role.
4. Retest the same page and action using the affected user's account.

If one user succeeds and another fails, compare their actual assignments rather than relying only on a role's display name.

See [App and data permissions](https://docs.jetadmin.io/access-and-sharing/app-and-data-permissions).

## Still getting 403?

Send support the app URL, environment, affected page/action, expected role, and time of the failed attempt. State whether signing in again changed the result and whether other users are affected.

Share the error text or a sanitized screenshot, not session cookies or JWT tokens. Avoid granting administrator access as a workaround for an unexplained permission difference.

*Last reviewed: September 16, 2026.*


---

# 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/faq-and-troubleshooting/403-and-user-permission-errors.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.