
Use Zitadel projects, granted organizations, and user metadata to power fine-grained authorization decisions in Cerbos policies.
Reference Zitadel project roles and organization grants directly in Cerbos policies for per-project authorization
Write authorization rules that account for Zitadel's organization grant model, enabling cross-org access control
Both Zitadel and Cerbos can run self-hosted or in the cloud, giving you deployment flexibility without architecture changes
Zitadel handles authentication, confirming who a user is. Cerbos handles authorization, deciding what that user can do. Together they give you a complete access control stack without coupling identity logic to business rules.
Cerbos lets you write fine-grained, context-aware authorization policies in human-readable YAML. Policies are decoupled from application code so product and security teams can update permissions without a release cycle.
Because Cerbos runs as a stateless Policy Decision Point (PDP) next to your application, authorization checks are sub-millisecond and scale horizontally with your infrastructure.
Zitadel structures identity around projects, organizations, and grants, a model designed for B2B and multi-tenant applications. Cerbos uses that structure to make fine-grained authorization decisions, going beyond what Zitadel's built-in role checks can express.
Zitadel's organization grant model lets one organization grant another access to its projects with specific roles. Cerbos policies can use this grant context to enforce fine-grained access rules: different permissions for users from the owning organization versus granted organizations, resource-level restrictions based on organization membership, and conditional rules based on project-specific roles.
Check out the Cerbos documentation to learn how to pass Zitadel token claims to Cerbos for policy evaluation.
Yes. Zitadel's project roles and organization grants are included in OIDC token claims. Your application passes these to Cerbos as principal attributes, where policies can reference project-scoped roles and granted organization context for authorization decisions.
Zitadel supports B2B scenarios where organizations grant access to other organizations' projects. The granting organization ID and project roles can be passed to Cerbos, enabling policies that enforce different access rules depending on which organization the user belongs to and which project they are accessing.
Yes. Zitadel allows custom key-value metadata on users and organizations. When included in token claims via actions, this metadata can be passed to Cerbos as principal attributes and used in policy conditions.



What is Cerbos?
Cerbos is an end-to-end enterprise authorization software for Zero Trust environments and AI-powered systems. It enforces fine-grained, contextual, and continuous authorization across apps, APIs, AI agents, MCP servers, services, and workloads.
Cerbos consists of an open-source Policy Decision Point, Enforcement Point integrations, and a centrally managed Policy Administration Plane (Cerbos Hub) that coordinates unified policy-based authorization across your architecture. Enforce least privilege & maintain full visibility into access decisions with Cerbos authorization.