> 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/sign-in-sign-up.md).

# App SSO

In this section you will learn how to build Sign In/Sign Up Page

Connect your app to an external identity provider using the protocol supported by your organization.

## Provider guides

| Provider           | Setup guide                                                                                                                                                                            |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Auth0              | [OAuth 2.0](/access-and-sharing/authentication-and-sso/sign-in-sign-up/auth0-sso-oauth-2.0.md) or [SAML2](/access-and-sharing/authentication-and-sso/sign-in-sign-up/auth0-sso.md)     |
| Microsoft Azure AD | [OAuth 2.0](/access-and-sharing/authentication-and-sso/sign-in-sign-up/auth0-sso-oauth-2.0-1.md)                                                                                       |
| Okta               | [Okta SSO](/access-and-sharing/authentication-and-sso/sign-in-sign-up/okta-sso.md)                                                                                                     |
| Google             | [OAuth 2.0](/access-and-sharing/authentication-and-sso/sign-in-sign-up/google-oauth-2.0.md) or [SAML2](/access-and-sharing/authentication-and-sso/sign-in-sign-up/google-sso-saml2.md) |
| Custom provider    | [OAuth 2.0](/access-and-sharing/authentication-and-sso/sign-in-sign-up/custom-sso-oauth-2.0.md)                                                                                        |

## Start in the current builder

Open **More → Authentication → Add External Authentication**, then select the appropriate provider. Existing provider tutorials may show earlier navigation and identity-provider screens; use the values displayed in your current configuration.

Confirm the app environment, redirect or callback values, identity mapping, and team assignment before rollout. Test successful sign-in and rejection of an unintended account, while retaining a working administrator sign-in path.

If your API needs the authenticated user's token, see [API calls with SSO token](/access-and-sharing/authentication-and-sso/sign-in-sign-up/api-calls-with-sso-token.md).

## Classic sign-in page customization

The earlier sign-in page editor offered visual customization for login and signup screens. That workflow is separate from configuring an identity provider. Use the authentication settings above for the current builder.

If sign-in or redirects fail, continue with [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/sign-in-sign-up.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.