Manage Access
Give people access to a project through groups. An OrganizationUserGroup manifest defines a group. The permissions block of a project lists groups. Each change is a pull request, so Git records who asked, and who approved it when a rule requires approval.
For the exact Google Cloud permissions of each tier, read Access Tiers.
Prerequisites
- An
OrganizationUsermanifest for each person. - The name of the project and its environment.
Steps
-
Add the person to a group. List the
OrganizationUsername, not an email address.apiVersion: lowops.manifests.v1
kind: OrganizationUserGroup
metadata:
name: payments-contributors
organization: acme-corp
spec:
description: Developers with contribution access to AstraPay production.
members:
users:
- tech-lead
- jane-smith # added
external: [] -
Reference the group in the
permissionsblock of theProject.apiVersion: lowops.manifests.v1
kind: Project
metadata:
name: astrapay-prod
environment: production
organizational-unit: payments
organization: acme-corp
spec:
permissions:
administrators:
groups: [platform-team]
contributors:
groups: [payments-contributors]
viewers:
groups: [qa-team] -
Commit the change in a pull request and merge it.
You can ask Beck to open this pull request. Say, for example, "Add jane-smith to the payments-contributors group". See Use Beck.
Rules
groupsaccepts only themetadata.nameof anOrganizationUserGroup. It does not accept a Google group email or a GitHub team name. The group manifest does the sync with the outside identity system. If that system changes, the project manifests stay as they are.- Prefer
groupstomembers. One edit to a group changes access in every project that lists the group. Use groups for production projects. - To remove access, delete the user from the group, or delete the group from the
permissionslist. - For temporary access, use a group with a date in its name, such as
security-auditors-2026-q4. Put the end date in a comment. - Permissions inherit down the hierarchy, and lower levels add to them. See The Security Framework.
Verify
Check the IAM bindings of the project in the Google Cloud console. Ask the person to open the project resources that their tier allows.