> 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/authentication-and-sso/choose-an-authentication-method/auth0.md).

# Auth0

Choose the Auth0 guide that matches your organization's authentication protocol.

* [Auth0 with OAuth 2.0](/access-and-sharing/authentication-and-sso/sign-in-sign-up/auth0-sso-oauth-2.0.md)
* [Auth0 with SAML2](/access-and-sharing/authentication-and-sso/sign-in-sign-up/auth0-sso.md)

## Before configuration

Confirm which protocol your identity administrator intends to use and which app environment you are configuring. Use the callback, redirect, or service-provider values displayed for that environment.

In the current builder, begin at **More → Authentication → Add External Authentication**. The selector includes **Auth0 OAuth 2.0**. Provider guides may show earlier navigation or provider-console layouts.

## Verify the integration

Test with an intended Auth0 account and check the identity that arrives in Jet Admin, its team assignment, and its access to the published app. Include an account that should not have access.

Keep an existing administrator sign-in available until the new flow is working. If authentication succeeds but the user sees the wrong records or actions, investigate [authorization](/access-and-sharing/app-and-data-permissions.md) separately from the identity-provider setup.

For errors and redirect loops, use [Troubleshoot sign-in](/access-and-sharing/authentication-and-sso/troubleshoot-sign-in.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/authentication-and-sso/choose-an-authentication-method/auth0.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.