> 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/jet-auth-and-built-in-sign-in.md).

# Jet Auth and built-in sign-in

Review built-in sign-in options when you do not need to start with a separate identity-provider integration.

## Find the controls

1. Open **More → Authentication**.
2. Locate the **Built-in** section.
3. Review the sign-in options and their scope labels.
4. Configure the options intended for your app's audience.
5. Test the published app with a separate intended user.

The current screen shows:

| Option                | Scope label shown |
| --------------------- | ----------------- |
| Sign in with Google   | Jet Admin app     |
| Sign in with Facebook | Jet Admin app     |
| Sign in with Email    | This App users    |

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

Read the scope label before changing an option; the controls do not all describe the same audience.

## Verify before rollout

Confirm that the intended user can enter the published app and receives the expected team and permissions. Also test an account that should not receive access.

Keep a working administrator sign-in path while changing authentication. An enabled sign-in option is not evidence that every authenticated account should become an app member.

For onboarding, use [email invitations](/access-and-sharing/members-users-and-groups/invite-by-email.md). For login failures, use [Troubleshoot sign-in](/access-and-sharing/authentication-and-sso/troubleshoot-sign-in.md). For an external identity system, continue with [Choose an authentication method](/access-and-sharing/authentication-and-sso/choose-an-authentication-method.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/jet-auth-and-built-in-sign-in.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.