Skip to content

tutorials

Intended Documentation

Platform Jobs-to-be-Done

Persona-based guide to the Intended documentation and the workflows each role should follow.

beginner3 min readimplemented

Overview#

Intended serves four primary personas. This guide maps each persona to their key workflows and the documentation that supports them.

Operator#

Who: Platform operators who manage policies, deployments, and runtime health.

Key workflows:

Author and validate policies

Create governance policies, validate them locally, and prepare for review.

Documentation: Author Policy Safely

Simulate policy changes

Run impact analysis before deploying — compare mode, drift detection, blast radius.

Documentation: Simulate Impact

Deploy and manage policies

Stage, approve, deploy, and roll back policy versions.

Documentation: Approve, Deploy & Rollback

Investigate incidents

Query audit trails, inspect decision tokens, and use emergency controls.

Documentation: Investigate Incidents

Also relevant:

Enterprise Administrator#

Who: Platform administrators who manage tenants, roles, tokens, and compliance.

Key workflows:

Set up tenant trust boundaries

Create tenants, configure isolation modes, manage member access.

Documentation: Tenant & Trust Boundary

Manage roles and API tokens

Assign roles, create/rotate API tokens, enforce least-privilege.

Documentation: Roles & Token Governance

Export audit evidence

Generate compliance packs, configure retention, stream audit events.

Documentation: Audit Export & Evidence

Use emergency controls

Activate kill switches, trigger circuit breakers, revoke tokens in bulk.

Documentation: Emergency Controls

Also relevant:

Developer#

Who: Engineers integrating Intended into applications and services.

Key workflows:

Get started with the API

Obtain an API key, submit your first intent, inspect the decision token.

Documentation: Quickstart then API Quickstart

Verify decision tokens

Validate token signatures, inspect claims, handle expiration.

Documentation: Verify Tokens & Decisions

Enforce decisions in application code

Integrate the enforcement SDK as middleware in your application.

Documentation: Enforcement SDK

Handle errors and edge cases

Understand error codes, implement retry strategies, troubleshoot failures.

Documentation: Error Patterns & Remediation

Also relevant:

Security & Compliance Engineer#

Who: Engineers responsible for security posture, audit compliance, and risk assessment.

Key workflows:

Verify enforcement lineage

Trace every authorization decision from policy through evaluation to enforcement.

Documentation: Enforcement Lineage

Understand fail-closed controls

Review how the platform behaves during failures and outages.

Documentation: Fail-Closed Controls

Run operational readiness checks

Validate system health, run pre-launch checklists, verify security controls.

Documentation: Operational Readiness

Also relevant:

Next Steps#