prod and staging. Grants, scopes, and guardrails can then say where a role or a statement applies.
Projects are optional. An organization that never creates one keeps everything in default and can ignore projects entirely. Leaving projects out of a grant or a statement means every project, and every rule works the same either way.
What Sits in a Project
- Only resources sit in projects. Users, service accounts, and roles belong to the organization, and a grant says which projects each one reaches.
- Each resource sits in exactly one project. That makes a project a boundary, not a tag. Access given in
stagingnever reaches a resource inprod. - Projects sit directly under the organization and do not nest. They are never a billing unit. Managed organizations are for separate bills.
Setting Projects Up
- Create the project. Someone holding
iam.projects.create, such as an Org Admin, names it. - Build new resources into it. The product’s own create request names the project, and the requester needs permission in that project. A resource created without one lands in
default. - Move existing resources in. Moving a resource needs permission in both its old and its new project, so nobody can pull a resource out of
prodwithout access toprod.
Where Projects Are Used
- In a grant, a role applies only to resources in the named projects.
- In a scope, an API key is held to the named projects, even when its user reaches further.
- In a guardrail, a deny protects a project from everyone, the owner included.
- In lists, such as
GET /v2/phone_numbers, a request returns only resources in projects the requester may read.
staging and only reads prod.