> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/notifications/basic-notifications/add-firebase-user.md).

# Add Firebase user

### How to add a user to your Firebase account?

On Firebase, you can use the Permissions interface to invite your team members and colleagues to collaborate. 

Assign a role to each member you invite based on the level of access needed. Watch the video tutorial below to add a user to your Google Firebase account:

{% embed url="<https://scribehow.com/shared/Add_Firebase_user__VsjYpWTZR3ujfeHMZTs-YA>" %}

The following steps explain the process in detail:

* Login to your Firebase account and choose the project you wish to invite your team members to.&#x20;
* Your project dashboard screen will appear.&#x20;
* Click on the Settings icon next to Project Overview.
* Select Users and Permissions.&#x20;
* Click on Add member. You’ll next have to enter the email address and role of the team member you invite.&#x20;
* Your team member will be able to access your Firebase account based on the role you assign.&#x20;

Firebase enables you to broadly choose between four roles:

* Viewer: Best for team members who only need to read existing data and resources on your Firebase account.&#x20;
* Editor: Best for team members that need to change existing resources frequently.&#x20;
* Owner: Best for team members who need to setup billings, manage roles & permissions, and delete & restore projects.&#x20;

{% hint style="warning" %}
Firebase roles: These roles work best when you wish to grant granular access to specific modules of your Firebase account.
{% endhint %}


---

# 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.appmysite.com/app/notifications/basic-notifications/add-firebase-user.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.