# Least privilege for human users in Google Cloud means predefined roles for groups at the smallest scope

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Human users in Google Cloud get permissions when IAM roles are granted to users and groups in allow policies. Google's documentation, read 16 Nov 2026, names the IAM recommender, Policy Troubleshooter, Policy Analyzer and Policy Simulator as the provider tools. This guide gives the steps, the roles to avoid and the measures.

## People get Google Cloud permissions from roles granted in allow policies

An IAM allow policy binds principals to roles on a resource, and Google's documentation says child resources inherit the allow policies of their parents. Its example: if a project policy lets a user administer Compute Engine VMs, the user can administer any VM in the project, whatever is set on an individual VM.

Google's IAM security guidance therefore says to grant roles at the smallest scope needed and to grant roles to groups instead of individual users when possible.

Google describes three kinds of role. Basic roles (Owner, Editor, Viewer, with newer Admin, Writer and Reader equivalents) are broad. Predefined roles are service-specific. Custom roles are ones you define. Google says basic roles include thousands of permissions across all services and that in production you should not grant them unless there is no alternative.

Google also says project creators are automatically granted the Owner role on the new project. That is the first place [privilege creep](/privilege-creep/) starts in Google Cloud.

## The IAM recommender, Policy Troubleshooter and Policy Simulator are Google's tools for this identity type

The IAM recommender produces role recommendations that suggest removing or replacing roles that give excess permissions. Google says it compares a principal's permissions with the permissions it used in the last 90 days, or since the grant if the role was granted fewer than 90 days ago. It also uses a machine learning model to keep permissions the principal is likely to need, which Google marks with a distinct symbol in the comparison view.

Policy Intelligence is the name Google gives to a set of tools. Policy Analyzer for allow policies finds which principals have access to which resources. Policy Troubleshooter takes a principal, a resource and a permission and examines the allow, deny and Principal Access Boundary policies to say whether access is allowed. Policy Simulator shows how a policy or role change would affect access before you make it.

Google's IAM security guidance suggests using the recommender and Policy Simulator when replacing a basic role, and conditional role bindings so access expires automatically, with temporary elevated access for administrators.

Google's documentation states that recommendations are not generated for every role granted to a principal, so absence of a recommendation does not show a role is right-sized.

## Steps to bring human access in Google Cloud to least privilege

- Use Policy Analyzer to list who holds roles/owner, roles/editor and other basic roles across the organization, and at which level.
- Move individual users into Google groups and grant roles to the groups.
- For every basic role, review the IAM recommender suggestion and the role's predefined replacement. Test the swap in Policy Simulator before applying.
- Move grants from the organization or folder to the project or resource that needs them.
- Convert standing admin grants to time-limited conditional bindings or temporary access.
- Limit who can modify allow policies: Google notes that roles such as Project IAM Admin and Folder IAM Admin let holders change policies without direct resource access.
- Use Policy Troubleshooter when a removal causes a denied request, to see which policy applies.
- Reapply the recommender review on a fixed cycle. [The first 90 days](/first-90-days/) suggests an order.

## Roles to avoid for human users

| Role | Documented reason (Google, read 16 Nov 2026) | Use instead |
| --- | --- | --- |
| roles/owner | Google says it allows access to and modification of almost all resources, including allow policies, and to grant it only when nearly universal access is required. | A predefined admin role for one service, at project scope. |
| roles/editor | Google says it lets you create and delete resources for most services; it is a legacy basic role that cannot take IAM Conditions. | A predefined role for the services the person uses. |
| roles/viewer | Google says basic roles include thousands of permissions across all services. | A service-specific viewer role. |
| Service Account User on a project | Google says holders can access every resource the service account can access. | The role on one service account only. |
| Project IAM Admin or Folder IAM Admin for routine tasks | Google says these roles allow modifying allow policies. | Narrow admin roles; grant these through temporary access. |
| Any role at organization scope when one project needs it | Google says allow policies inherit down the hierarchy. | Grant at the project or resource. |

## Measure permissions granted against permissions used in the last 90 days

The IAM recommender's own window gives the unit. For each human principal and role, record the number of permissions in the role and the number the principal used in the last 90 days, and keep the unused share per role. Record the count of principals with basic roles, split by Owner and Editor, and the count of grants made directly to users rather than groups.

These counts are available without any new tool: Policy Analyzer gives the first two and Cloud Asset data the third. The [Access Debt Calculator](/) turns granted and used counts into a single figure. [The principle of least privilege](/principle-of-least-privilege/) explains why the unit is the permission.

Related guides: [AWS human identities](/guides/aws-human-identities/) and [Azure human identities](/guides/azure-human-identities/).

## Related pages

- [Least privilege for service identities in Google Cloud](/guides/google-cloud-service-identities/)
- [Least privilege for workload identities in Google Cloud](/guides/google-cloud-workload-identities/)
- [Least privilege for third-party identities in Google Cloud](/guides/google-cloud-third-party-identities/)
- [All of them](/guides/)

## Sources

- Google Cloud IAM: Best practices for using IAM securely: https://cloud.google.com/iam/docs/using-iam-securely (read 16 Nov 2026)
- Google Cloud IAM: Roles and permissions: https://cloud.google.com/iam/docs/roles-overview (read 16 Nov 2026)
- Google Cloud IAM: Role recommendations overview: https://cloud.google.com/iam/docs/recommender-overview (read 16 Nov 2026)
- Google Cloud IAM: Manage role recommendations: https://cloud.google.com/iam/docs/recommender-managing (read 16 Nov 2026)
- Google Cloud: Policy Intelligence overview: https://cloud.google.com/policy-intelligence/docs/overview (read 16 Nov 2026)
- Google Cloud IAM: Troubleshoot permissions: https://cloud.google.com/iam/docs/troubleshooting-access (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://leastprivilegeprinciple.com/guides/google-cloud-human-identities/
