Core concepts
ZStrike externalizes authorization: instead of scattering permission checks through your codebase, you write policies centrally and ask the platform for decisions at runtime.
ZStrike is built on Cedar, the open-source authorization policy language. A Cedar policy states who (principal) can do what (action) on which resource, under what conditions:
permit ( principal in App::Team::"engineering", action == App::Action::"read", resource in App::Folder::"design-docs");Cedar is deny-by-default: a request is only allowed if at least one permit policy matches and no forbid policy does.
Organizations and projects
Section titled “Organizations and projects”Tenancy is two-level:
- An organization is your company. Members, credentials, and audit storage are scoped to it.
- A project is an application or environment within the organization. Policies, schemas, and entities live per project, and the Policy Decision Point serves decisions per project.
Schema
Section titled “Schema”Each project has a Cedar schema describing your domain: the entity types that exist (users, teams, documents…), the attributes they carry, and the actions that can be performed on them. The schema powers policy validation — the platform can tell you a policy references an attribute that doesn’t exist before it ever affects a decision.
Entities
Section titled “Entities”Entities are the data your policies evaluate over: concrete users, groups, resources, and their attributes and parent relationships. An entity has a typed identifier (App::User::"alice"), attributes, and parents (for in hierarchy checks).
Entities are managed centrally in the platform’s entity store and distributed automatically to the decision points. Your application does not ship entity data with each authorization request. The only exception is narrow: a resource not yet synced may be attached inline under a dedicated app-token grant (details).
Policies
Section titled “Policies”Policies are authored per project — in the Console’s editor or through the API — validated against the project’s schema, versioned, and distributed to the decision points that serve your applications.
The decision
Section titled “The decision”At runtime your application asks: may this principal perform this action on this resource, given this context? The Policy Decision Point answers Allow or Deny in milliseconds, along with the policies that determined the outcome. Every decision is recorded as an audit event.
App tokens
Section titled “App tokens”App tokens are the platform’s machine credentials. They are scoped to an organization or a single project, carry fine-grained permissions, and always expire. Your services use app tokens to call the platform’s APIs.
Glossary
Section titled “Glossary”| Term | Meaning |
|---|---|
| PAP | Policy Administration Point — the control plane where policies, schemas, and entities are managed. |
| PDP | Policy Decision Point — the engine that evaluates Cedar policies and answers authorization requests. |
| Principal | The entity attempting an action (a user, service, or token). |
| Resource | The entity an action targets. |
| Entity | A typed object with attributes and parents, e.g. App::User::"alice". |
| Schema | The typed description of your entity types and actions. |
| Audit event | The durable record of one authorization decision. |
| App token | A scoped, expiring machine credential for calling platform APIs. |