Skip to main content
A policy limits what a credential can do. It’s a list of allow statements, each pairing one action with one resource, and everything it doesn’t list is denied. This page lists everything you can grant in a policy.

Where policies apply

Three kinds of credential carry a policy, and all three use the same format: Every resource in a policy must be inside its credential’s boundary. A few operations stay closed to federation rules and service account API keys whatever their policy grants. See what a service account can’t do. For a CI job, cloud service, or Kubernetes pod, put the policy on a federation rule instead of a stored key. See API authentication to choose.

Resources

Resources must be inside the credential’s boundary: the organization, or the one project for a project-scoped key, a federation rule, or a service account API key. Kernel checks that every object ID exists when you create or update the key or rule.

Conditions

A statement can carry one condition that narrows it to matching requests:
How conditions evaluate:
  • A condition only narrows its own statement. To restrict a whole credential, add the same condition to every statement.
  • Requests from outside every listed network get 403 with insufficient_scope, recorded in your audit logs with the client IP.
  • A scoped key can’t delegate a wider condition than it holds: a delegated key can narrow its parent’s IP rules, never loosen them.
  • You can add or change IP rules on an existing key without rotating its credential. See Limit a key to your IP ranges.

Actions

Browsers

Profiles

Vaults

Proxies

Operations that need more than one action

List endpoints return only the objects the credential can access, so a credential without a matching grant gets an empty list.

Not available to credentials with a policy

A credential with a policy gets 403 with insufficient_scope on:
  • API key management, including creating, listing, rotating, and deleting keys.
  • Browser pools.
  • Project and organization endpoints, such as listing projects or reading limits.
  • Creating browsers that use saved extensions, telemetry export, or app invocations.
  • Any other endpoint not covered by the actions above.