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

# Choose an authentication method

Choose the method that matches the identity system your app's users already have.

| Requirement                                | Start here                                                                                                                             |
| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
| Use built-in sign-in options               | [Jet Auth](/access-and-sharing/authentication-and-sso/choose-an-authentication-method/jet-auth-and-built-in-sign-in.md)                |
| Use Firebase identities                    | [Firebase Auth](/access-and-sharing/authentication-and-sso/choose-an-authentication-method/firebase-auth.md)                           |
| Use Supabase identities                    | [Supabase Auth](/access-and-sharing/authentication-and-sso/choose-an-authentication-method/supabase-auth.md)                           |
| Use Auth0                                  | [Auth0](/access-and-sharing/authentication-and-sso/choose-an-authentication-method/auth0.md)                                           |
| Use a company OAuth or SAML provider       | [App SSO](/access-and-sharing/authentication-and-sso/sign-in-sign-up.md)                                                               |
| Use an existing custom or token-based flow | [Token-based authentication](/access-and-sharing/authentication-and-sso/choose-an-authentication-method/token-based-authentication.md) |
| Use Xano authentication                    | [Xano Auth](/access-and-sharing/authentication-and-sso/choose-an-authentication-method/xano-auth.md)                                   |

## Open external authentication

1. Open **More → Authentication**.
2. Find **External Authentication**.
3. Select **Add External Authentication**.
4. Choose the provider that matches your identity system.
5. Follow its configuration form and the corresponding guide.

Use the callback or redirect values displayed for your own app. An example app's URL is not a substitute.

![More settings with Authentication selected and Add External Authentication visible](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2F8Vdpvia6gcq5TMcCuC83%2Fauthentication-settings.jpg?alt=media)

Open More → Authentication to find the built-in options and Add External Authentication.

![External authentication provider menu with Firebase, Supabase, Google, and Auth0 options](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2Fx5DGqMsXxj0mEAUE22cJ%2Fexternal-auth-provider-menu.jpg?alt=media)

Select the provider that matches your identity system; configure it using the values for your own app.

## Prepare the identity mapping

Before rollout, identify the account attribute used to match users, how users become members, how teams are assigned, and what happens to users who have no assignment.

Test these assumptions with an intended user and a user who should not receive access. Retain an existing working sign-in path until the new method and access rules are verified.


---

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