# Principal access boundary

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

A Google Cloud IAM policy attached to a set of principals that defines which resources those principals are eligible to access. If a principal is ineligible for a resource, access is limited whatever roles the principal holds. Its scope is the principal, not the resource.

## An example, sourced

Google documents that "by default, principals are eligible to access any Google Cloud resource." With a Principal Access Boundary policy you can define the resources a principal is eligible to access. The page gives an example use: preventing principals from accessing resources in other organizations, which can help prevent phishing. These policies attach to principal sets, unlike allow policies, which attach to resources.

## Why it matters here

This is Google's nearest analog of a permissions boundary, set around identities. The library covers it as a mechanism with its own entry. This is Google's nearest analog of a permissions boundary, and it is set around identities and not resources. The library covers it as its own mechanism with one entry, which you can use as a starting point.

## Related pages

- [Guardrail: meaning and an example](/glossary/guardrail/)
- [Preventive control: meaning and an example](/glossary/preventive-control/)
- [Detective control: meaning and an example](/glossary/detective-control/)
- [All of them](/glossary/)

## Sources

- https://cloud.google.com/iam/docs/principal-access-boundary-policies (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/glossary/principal-access-boundary/
