Identity and Access Management(IAM)를 사용하면 구체적인 Firebase 및 Google 리소스에 더욱 세분화된 액세스 권한을 부여하고 다른 리소스에 대한 무단 액세스를 방지할 수 있습니다.
IAM은 최소 권한의 보안 원칙을 채택하여 리소스에 대해 필요한 액세스 권한만 부여할 수 있게 해줍니다.
Firebase는 Firebase 프로젝트와 프로젝트 구성원 전용의 추가 IAM 옵션을 제공합니다.
인증된 프로젝트 구성원이 Firebase에서 작업을 요청하면 IAM은 이 프로젝트 구성원이 리소스에 요청한 작업을 수행할 수 있는 권한이 있는지 확인하여 승인합니다. 프로젝트 구성원이 요청을 수행할 수 있는지 여부는 프로젝트 구성원에게 할당된 역할에 따라 다릅니다.
각 역할은 권한의 모음이며 프로젝트 구성원에게 역할을 할당하면 해당 역할의 모든 권한을 해당 구성원에게 부여하는 것입니다.
프로젝트 구성원
Firebase IAM을 사용하여 프로젝트 구성원에게 역할과 그 역할에 내재된 권한을 할당합니다. 프로젝트 구성원의 유형은 다음 중 하나일 수 있습니다.
Google 계정
서비스 계정
Google 그룹
역할
권한은 역할을 통해 프로젝트 구성원에게 부여됩니다. 역할은 권한 모음입니다. 프로젝트 구성원에게 역할을 할당하면 역할에 포함된 모든 권한이 프로젝트 구성원에게 부여됩니다.
Google Cloud 콘솔은 IAM 페이지에서 프로젝트 구성원에게 역할을 할당할 수 있는 다양한 도구 모음을 제공합니다. 또한 Cloud 콘솔에서 커스텀 역할을 만들고 관리할 수 있을 뿐만 아니라 서비스 계정에 프로젝트에 대한 액세스 권한을 부여할 수 있습니다.
Google Cloud 콘솔에서는 프로젝트 구성원을 주 구성원이라고 합니다.
프로젝트 소유자가 더 이상 소유자의 작업을 수행할 수 없으며(예: 직원 퇴사) 프로젝트가 Google Cloud 조직을 통해 관리되지 않는 경우(다음 단락 참조) Firebase 지원팀에 문의하여 Firebase 프로젝트에 대한 액세스 권한을 요청하는 방법을 확인할 수 있습니다.
Firebase 프로젝트가 Google Cloud 조직에 속한 경우 소유자가 없을 수 있습니다.
Firebase 프로젝트의 소유자를 찾을 수 없으면 Google Cloud 조직의 관리자에게 프로젝트의 소유자를 할당해 달라고 요청하세요.
[null,null,["최종 업데이트: 2025-08-04(UTC)"],[],[],null,["# Manage project access with Firebase IAM\n\nIdentity and Access Management (IAM) lets you grant granular access to specific\nFirebase and Google resources and prevents unwanted access to other resources.\nIAM lets you adopt the\n[security principle of least privilege](//en.wikipedia.org/wiki/Principle_of_least_privilege),\nso you grant only the necessary access to your resources.\n\nFor a detailed description of IAM, read the\n[Google Cloud IAM documentation](//cloud.google.com/iam/docs/).\n\nOverview of Firebase IAM\n------------------------\n\nFirebase offers additional IAM options that are specific for Firebase projects\nand your project members.\n\nWhen an authenticated [**project member**](#members) requests an action in\nFirebase, IAM makes an authorization decision about whether the project member\nhas [**permission**](/docs/projects/iam/permissions) to perform the requested\noperation on the **resource** . Whether the project member is allowed to perform\nthe request depends on the project member's assigned [**role**](#roles).\nEach role is a collection of permissions, and when you assign a role to a\nproject member, you are granting that project member all the permissions for\nthat role.\n\nProject members\n---------------\n\nUsing Firebase IAM, you assign roles (and their inherent permissions) to your\nproject members. Project members can be of the following\n[types](//cloud.google.com/iam/docs/overview#concepts_related_identity):\n\n- Google account\n- Service account\n- Google group\n\n| **Note:** In the Google Cloud console and Google Cloud IAM documentation, project members are called *principals*.\n\nRoles\n-----\n\n**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\n--------------------------------------\n\n| **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\n### View project members and their roles\n\nYou 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\n### Assign 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."]]
