Stay organized with collections
Save and categorize content based on your preferences.
Basic roles (Owner, Editor, and Viewer) are fundamental roles for IAM
and include different levels of access permissions for all the Firebase products
and services.
The following table summarizes the permissions included in each role. Learn more
about basic roles
in the Google Cloud documentation.
Note that basic roles were formerly called "primitive" roles.
Permissions for read-only actions, such as viewing (but not modifying)
existing resources or data.
Editor roles/editor
All the Viewer role permissions, plus permissions for actions
that modify state, such as changing existing resources.
Owner roles/owner
All the Editor role permissions, plus permissions for the
following actions:
Manage roles and permissions for a project and all resources
within the project.
Set up billing for a project.
Delete or restore a project.
Importance of assigning the Owner role
To ensure proper management of a Firebase project, it must have an
Owner.
Project members with the Owner role are
often the only project members who can do administrative
tasks or receive important notifications:
Project members with the Owner role are often the only members who can
perform important administrative actions (like assigning roles and managing
Google Analytics properties), and Firebase Support can only fulfill
administrative requests from demonstrated project Owners.
Project members with the Owner role are often the only members who
(by default) receive notifications about changes to the project or products
(like billing and legal changes, deprecations of features, etc.).
You can optionally
customize your project's "essential contacts"
if you want specific or additional project members to receive notifications.
After you set up the Owner(s) for a Firebase project, it's important to
keep those assignments up-to-date.
Note that if a Firebase project is part of a Google Cloud organization, the
person who manages your Google Cloud organization can perform many tasks
that an Owner can do. However, for several Owner-specific tasks (like
assigning roles or managing Google Analytics properties), the
administrator may need to assign themselves the
actual Owner role to perform
those tasks.
[[["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-15 UTC."],[],[],null,["**Basic roles** (Owner, Editor, and Viewer) are fundamental roles for IAM\nand include different levels of access permissions for all the Firebase products\nand services.\n\nThe following table summarizes the permissions included in each role. Learn more\nabout [basic roles](//cloud.google.com/iam/docs/understanding-roles#basic)\nin the Google Cloud documentation.\n\nNote that basic roles were formerly called \"primitive\" roles.\n\nAssign these roles to project members using the\n[Firebase console](https://console.firebase.google.com/project/_/settings/iam)\nor the\n[Google Cloud console](https://console.cloud.google.com/iam-admin/iam).\n| **Note:** Assigning roles using the Google Cloud console is helpful if you don't have access to open the Firebase project via the Firebase console (for example, you're the administrator of the project's Google Cloud organization).\n\n| Role | Permissions |\n|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| **Viewer** `roles/viewer` | Permissions for read-only actions, such as viewing (but not modifying) existing resources or data. |\n| **Editor** `roles/editor` | All the Viewer role permissions, **plus** permissions for actions that modify state, such as changing existing resources. | **Note:** The `roles/editor` role contains permissions to create and delete resources for most Firebase products and services. |\n| **Owner** `roles/owner` | All the Editor role permissions, **plus** permissions for the following actions: - Manage roles and permissions for a project and all resources within the project. - Set up billing for a project. - Delete or restore a project. |\n\nImportance of assigning the Owner role\n\nTo ensure proper management of a Firebase project, it must have an\n[Owner](/docs/projects/iam/roles-basic).\n\nProject members with the Owner role are\n**often the *only* project members who can do administrative\ntasks or receive important notifications**:\n\n- Project members with the Owner role are often the only members who can perform important administrative actions (like assigning roles and managing Google Analytics properties), and Firebase Support can only fulfill administrative requests from demonstrated project Owners.\n- Project members with the Owner role are often the only members who (by default) receive notifications about changes to the project or products (like billing and legal changes, deprecations of features, etc.). You can optionally [customize your project's \"essential contacts\"](https://cloud.google.com/resource-manager/docs/managing-notification-contacts) if you want specific or additional project members to receive notifications.\n\nAfter you set up the Owner(s) for a Firebase project, it's important to\nkeep those assignments up-to-date.\n\nNote that if a Firebase project is part of a Google Cloud organization, the\nperson who manages your Google Cloud organization can perform many tasks\nthat an Owner can do. However, for several Owner-specific tasks (like\nassigning roles or managing Google Analytics properties), the\nadministrator may need to assign themselves the\n[actual Owner role](/docs/projects/iam/roles-basic) to perform\nthose tasks."]]