Stay organized with collections
Save and categorize content based on your preferences.
Permissions are granted to your project members via
roles. A role is a collection of
permissions. When you assign a role to a
project member, you grant that project member all the permissions that the role
contains.
Firebase IAM supports the following types of roles:
Basic roles:
Fundamental Owner, Editor, and Viewer roles (formerly called
"primitive" roles).
Predefined roles:
Curated Firebase-specific roles that enable more granular access control than
the basic roles. Firebase offers:
Firebase-level roles:
Roles which grant full read/write or read-only access to all the
Firebase products.
Product-category roles:
Roles which grant full read/write or read-only access to groups of
products. They are structured around Google Analytics and general
product categories.
Product-level roles:
Roles which grant full read/write or read-only access to specific
Firebase products.
Custom roles: Fully customized
roles that you create to tailor a set of permissions that meet the specific
requirements of your organization.
Manage project members and their roles
View project members and their roles
You can view many of your project members and their roles in the
Users and permissions tab
of settings > Project settings in the
Firebase console. Note the following:
The Firebase console only lists project members assigned a
basic role (Owner, Editor,
Viewer) or a
Firebase predefined role.
The project members listed in this tab are the only project members who have
access to the Firebase project in the Firebase console.
The Firebase console does not list project members that are service
accounts. View these project members in the
IAM page
of the Google Cloud console.
Alternatively, you can view all of your project members and their roles in the
IAM page
of the Google Cloud console.
Assign a role to a project member
To manage the role(s) assigned to each project member, you must be an Owner of the Firebase
project (or be assigned a role with the permission
resourcemanager.projects.setIamPolicy).
Here are the places where you can assign and manage roles:
The Google Cloud console offers an expansive set of tools to assign roles to project members
in the
IAM page. In the Cloud console, you can also create
and manage
custom roles, as well as give service accounts
access to your project.
Note that in the Google Cloud console, project members are called principals.
If the Owner of your project can no longer perform the tasks of an Owner (for example, the person
left your company) and your project isn't managed via a Google Cloud organization (see next
paragraph), you can
contact Firebase Support
and check with them about how to request access to the Firebase project.
Note that if a Firebase project is part of a Google Cloud organization, it may not have an Owner.
If you're unable to find an Owner for your Firebase project, contact the person who manages your
Google Cloud organization to assign an Owner for the project.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["**Permissions are granted to your project members via\n[*roles*](/docs/projects/iam/roles).** A role is a collection of\n[*permissions*](/docs/projects/iam/permissions). When you assign a role to a\nproject member, you grant that project member all the permissions that the role\ncontains.\n\nFirebase IAM supports the following types of roles:\n\n- **[Basic roles](/docs/projects/iam/roles-basic)** :\n Fundamental **Owner** , **Editor** , and **Viewer** roles (formerly called\n \"primitive\" roles).\n\n- **[Predefined roles](/docs/projects/iam/roles-predefined)**:\n Curated Firebase-specific roles that enable more granular access control than\n the basic roles. Firebase offers:\n\n - [**Firebase-level roles**](/docs/projects/iam/roles-predefined-all-products):\n Roles which grant full read/write or read-only access to *all* the\n Firebase products.\n\n - [**Product-category roles**](/docs/projects/iam/roles-predefined-category):\n Roles which grant full read/write or read-only access to groups of\n products. They are structured around Google Analytics and general\n product categories.\n\n - [**Product-level roles**](/docs/projects/iam/roles-predefined-product):\n Roles which grant full read/write or read-only access to *specific*\n Firebase products.\n\n- **[Custom roles](/docs/projects/iam/roles-custom)**: Fully customized\n roles that you create to tailor a set of permissions that meet the specific\n requirements of your organization.\n\nManage project members and their roles **Note** : Access changes, such as assigning a role or denying a permission, may take several minutes to take effect across all systems. For details, see [Access change propagation](https://cloud.google.com/iam/docs/access-change-propagation) in the Google Cloud documentation.\n\nView project members and their roles You can view many of your project members and their roles in the [*Users and permissions* tab](https://console.firebase.google.com/project/_/settings/iam) of settings \\\u003e **Project settings** in the Firebase console. Note the following:\n\n- The Firebase console only lists project members assigned a [basic role](/docs/projects/iam/roles-basic) (Owner, Editor, Viewer) or a [Firebase predefined role](/docs/projects/iam/roles-predefined). The project members listed in this tab are the only project members who have access to the Firebase project in the Firebase console.\n- The Firebase console does not list project members that are service accounts. View these project members in the [*IAM* page](https://console.cloud.google.com/iam-admin/iam) of the Google Cloud console.\n\nAlternatively, you can view *all* of your project members and their roles in the [*IAM* page](https://console.cloud.google.com/iam-admin/iam) of the Google Cloud console.\n\nAssign a role to a project member\n\nTo manage the role(s) assigned to each project member, you must be an Owner of the Firebase\nproject (or be assigned a role with the permission\n`resourcemanager.projects.setIamPolicy`).\n\nHere are the places where you can assign and manage roles:\n\n- The Firebase console offers a simplified way to assign roles to project members in the [*Users and permissions* tab](https://console.firebase.google.com/project/_/settings/iam) of settings \\\u003e **Project settings** . In the Firebase console, you can assign any of the [basic roles](/docs/projects/iam/roles-basic) (Owner, Editor, Viewer), the [Firebase Admin/Viewer roles](/docs/projects/iam/roles-predefined-all-products), or any of the [Firebase predefined product-category\n roles](/docs/projects/iam/roles-predefined-category).\n- The Google Cloud console offers an expansive set of tools to assign roles to project members in the [*IAM* page](https://console.cloud.google.com/iam-admin/iam). In the Cloud console, you can also create and manage [custom roles](/docs/projects/iam/roles-custom), as well as give service accounts access to your project.\n\n Note that in the Google Cloud console, project members are called *principals*.\n\nIf the Owner of your project can no longer perform the tasks of an Owner (for example, the person\nleft your company) and your project isn't managed via a Google Cloud organization (see next\nparagraph), you can\n[contact Firebase Support](https://firebase.google.com/support/troubleshooter/contact)\nand check with them about how to request access to the Firebase project.\n\nNote that if a Firebase project is part of a Google Cloud organization, it may not have an Owner.\nIf you're unable to find an Owner for your Firebase project, contact the person who manages your\nGoogle Cloud organization to assign an Owner for the project."]]