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

# Authentication and SSO

Choose how users prove their identity, then test the access they receive after sign-in.

Open **More → Authentication** in the builder, or use the **Authentication** tab in the Users area.

![Authentication settings with Built-in and External Authentication sections](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2F0ODXu9KZAZFCeqJdCuTY%2F07-authentication.png?alt=media)

## Choose your path

* [Jet Auth and built-in sign-in](/access-and-sharing/authentication-and-sso/choose-an-authentication-method/jet-auth-and-built-in-sign-in.md) — review the built-in options.
* [Choose an authentication method](/access-and-sharing/authentication-and-sso/choose-an-authentication-method.md) — compare built-in and external authentication.
* [App SSO](/access-and-sharing/authentication-and-sso/sign-in-sign-up.md) — use the existing provider-specific setup guides.
* [Troubleshoot sign-in](/access-and-sharing/authentication-and-sso/troubleshoot-sign-in.md) — investigate login or redirect failures.

The External Authentication selector includes Firebase Auth, Supabase Auth, and OAuth providers. The exact provider configuration depends on the selected method.

## Finish configuration with a test

Keep a working administrator sign-in available while testing a new method. Use a separate intended test account to verify sign-in, identity, team assignment, and access to the published app.

Authentication and authorization are separate: a valid identity should only receive the permissions you intended. Continue with [the access test checklist](/access-and-sharing/overview/test-access.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.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.