> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/fabricate/self-hosting-fabricate/configuring-fabricate/sign-in-options.md).

# Sign-in options

You can configure Fabricate to enable users to sign in using one or more of the following SSO options:

* Google
* GitHub
* Microsoft Entra ID (formerly Azure)

On the login page, Fabricate displays an icon for each enabled option.

After you start Fabricate, you can also set up single sign-on (SSO). For more information, go to [Single sign-on (SSO)](/fabricate/fabricate-accounts-and-users/managing-account-membership/managing-account-users/single-sign-on-sso.md).

## Google

To allow your users to sign in through Google, in `.env`, uncomment and set the following:

```
GOOGLE_CLIENT_ID=  # Google OAuth 2.0 client ID.
GOOGLE_CLIENT_SECRET=  # Google OAuth 2.0 client secret.
```

## GitHub

To allow your users to sign in through GitHub, in `.env`, uncomment and set the following:

```
GITHUB_CLIENT_ID=  # GitHub OAuth app client ID.
GITHUB_CLIENT_SECRET=  # GitHub OAuth app client secret.
```

## Microsoft Entra ID

To allow your users to sign in through Microsoft Entra ID, in `.env`, uncomment and set the following:

```
AZURE_CLIENT_ID=	# Microsoft Entra ID application (client) identifier
AZURE_CLIENT_SECRET=	# Microsoft Entra ID client secret.
AZURE_TENANT_ID= # Microsft Entra ID tenant ID.
```


---

# 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.tonic.ai/fabricate/self-hosting-fabricate/configuring-fabricate/sign-in-options.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.