Skip to content

Quickstart

This walkthrough takes you from signing up to a live Allow decision from a Policy Decision Point.

Sign-in is passwordless: enter your email on the Get Started page and verify the one-time code. Then create your organization — the tenant that owns your projects, members, and audit data. Invite teammates by email; they receive an invitation they can preview and accept.

A project is an isolated authorization workspace — typically one application or environment. Create one from the Projects page.

In Schema, describe your domain: the entity types (users, teams, documents…), their attributes, and the actions that can be performed. Use the Monaco editor with Cedar syntax support, or the form-based Schema Builder. The schema powers validation everywhere else — policies that reference unknown types or attributes are flagged as you type.

In Policies, create your first Cedar policy:

permit (
principal in App::Team::"engineering",
action == App::Action::"read",
resource in App::Folder::"design-docs"
);

Policies are validated against your schema, versioned on every change, and can be activated or deactivated without deletion. You can also describe what you want in plain language and let the AI assistant draft the policy for you to review.

In Entities, create the data your policies evaluate over — users, teams, resources — with their attributes and parent relationships. (For bulk or continuous ingestion from your own systems, see Syncing entities.)

In Simulator, build a request — principal, action, resource, context — and run it. Evaluation happens in your browser against the project’s schema, policies, and entities, and shows the decision plus the policies that produced it. Set an expected result on each request to turn it into a pass/fail test case, and save request sets to re-run after policy changes.

In PDP, attach your project to a shared PDP in your region. You get a decision endpoint and a client token. The PDP syncs your project immediately.

Terminal window
curl -X POST https://<your-pdp-host>/authorize \
-H "Content-Type: application/json" \
-H "X-Client-Token: <your-client-token>" \
-d '{
"principal": "App::User::\"alice\"",
"action": "App::Action::\"read\"",
"resource": "App::Folder::\"design-docs\""
}'
{
"code": 200,
"data": {
"decision": "Allow",
"diagnostics": { "reason": ["policy0"], "errors": [] }
}
}

See Authorizing requests for identity-token validation, context, and error handling.

Open Live Request Logs in the Console. Every decision your application triggers streams in as it happens — principal, action, resource, decision, and the determining policy. Historical decisions are in Audit Logs, filterable by principal, resource, decision, and time range.