Quickstart
This walkthrough takes you from signing up to a live Allow decision from a Policy Decision Point.
1. Sign in and create an organization
Section titled “1. Sign in and create an organization”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.
2. Create a project
Section titled “2. Create a project”A project is an isolated authorization workspace — typically one application or environment. Create one from the Projects page.
3. Define your schema
Section titled “3. Define your schema”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.
4. Write a policy
Section titled “4. Write a policy”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.
5. Add entities
Section titled “5. Add entities”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.)
6. Test in the simulator
Section titled “6. Test in the simulator”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.
7. Attach a Policy Decision Point
Section titled “7. Attach a Policy Decision Point”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.
8. Authorize from your application
Section titled “8. Authorize from your application”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.
9. Watch it live
Section titled “9. Watch it live”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.
Next steps
Section titled “Next steps”- Call it from code: install the TypeScript SDK, or read Authorizing requests for the raw HTTP contract.
- Load real data: keep users, groups, and resources in sync with Syncing entities.
- Automate safely: create a scoped app token for your services and CI.
- Change policies with confidence: use the simulator and impact analysis before you ship.