Console
The Console is where you work with ZStrike day to day. Everything is scoped to the currently selected project, with tools grouped into Model, Test, and Operate.
Sign-in is passwordless — email plus a one-time code. Sessions are cookie-based, and everything the Console does goes through the Control Plane API, so any workflow you see in the UI can also be automated.
Schema
Section titled “Schema”Author your project’s Cedar schema (entity types, actions, and attribute shapes) in a Monaco editor with Cedar syntax support and live validation, or visually with the form-based Schema Builder, which supports multiple namespaces. Schemas are versioned.
Policies
Section titled “Policies”The policy workspace covers the full lifecycle:
- Author in a rich Cedar editor, with a condition builder for
when/unlessclauses. - Describe instead of write: an AI assistant can draft or revise a policy from a natural-language description, always for your review before saving.
- Validate against the project schema before a policy can affect anything.
- Analyze impact before saving. The Impact panel reports whether the change makes the project more or less permissive, and replays the last 24 hours of real traffic against it (details).
- Version: every change creates a new version, with single- and multi-policy diff views to see exactly what changed, and one-click restore of an earlier version.
- Activate / deactivate policies without deleting them.
Entities
Section titled “Entities”Create and browse the entities your policies evaluate over — principals, resources, groups — with a nested attribute editor for structured attributes and parent relationships. A search view filters by type, status, and free text.
Simulator
Section titled “Simulator”Build authorization requests (principal, action, resource, context) and evaluate them entirely in your browser using the same Cedar engine the platform runs — no live PDP required. Each request shows the decision and the policies that determined it. Attach an expected result to turn a request into a pass/fail test case, and save request sets to re-run as your policies evolve.
Test entities
Section titled “Test entities”Maintain a separate set of fixture entities for the simulator, so you can exercise policies against test scenarios without touching your project’s real entity data.
Operate
Section titled “Operate”Attach your project to a shared regional Policy Decision Point, view its status, and rotate its client token. Register trusted identity providers: the OIDC issuers whose end-user tokens your applications use, and how their claims map to Cedar principals. (Enforcement at the shared PDP is not yet active per project. See Trusted identity providers.)
Audit logs and live request logs
Section titled “Audit logs and live request logs”- Audit Logs — searchable, paginated decision history with filters for principal, action, resource, and allow/deny.
- Live Request Logs — a real-time WebSocket stream of decisions as they happen, with the determining policy for each.
Access management
Section titled “Access management”- Organization — members, roles, and email invitations at the tenant level.
- Manage Access — per-project roles:
ADMIN,WRITER,READER, andTESTER.
App tokens
Section titled “App tokens”From the Organization page, owners and admins issue machine credentials for calling the platform’s APIs. Each is scoped to the organization or a single project, with a fine-grained permission map and a mandatory expiry. The secret is shown once at creation. Tokens can be rotated (new secret, same settings) and revoked at any time, and the list shows every token with its status, scope, and expiry. See App tokens.
Projects
Section titled “Projects”Projects are created from the Projects page — empty, or pre-seeded from a demo template for exploring the platform. Each project has an overview dashboard (active policy and entity counts, quick link to live logs), settings, and a full export that bundles its schema, policies, entities, and tests.