> 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/firebase-auth.md).

# Firebase Auth

Use the Firebase Auth option when Firebase is the identity system for your app's audience.

## Start configuration

1. Open **More → Authentication**.
2. Under **External Authentication**, select **Add External Authentication**.
3. Choose **Firebase Auth**.
4. Complete the settings requested by the current provider form using your Firebase project's configuration.
5. Check any app or domain values against the environment you intend to use.

The provider selector identifies Firebase Auth as available on All plans. Confirm any additional requirements shown in your app when configuring it.

## Prepare a test

Use a Firebase test account intended for this app. Verify that sign-in resolves to the expected person, that membership and team assignment are correct, and that the published app grants only the intended access.

Keep provider secrets out of screenshots, client-side app code, and support messages. The fields and setup requirements depend on the provider form; do not copy another application's configuration.

If sign-in fails, record the time and visible error, check [System logs](/access-and-sharing/audit-logs-privacy-and-security/investigate-system-logs.md), and follow [the sign-in troubleshooting checklist](/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/choose-an-authentication-method/firebase-auth.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.