Kaiten
Authentication

Scopes Reference

Complete reference of all permission scopes available for API tokens.

Scopes Reference

Scopes control what a Service Account token (ksh_*) can access. They follow the pattern <action>:<module>.

Available Scopes

ScopeAccess
read:customersList and view customers
write:customersCreate, update, and delete customers
read:instancesList and view instances
write:instancesCreate, update, and delete instances
read:licensesList and view licenses
write:licensesCreate, update, and delete licenses
read:entitlementsList and view entitlements
write:entitlementsCreate, update, and delete entitlements
read:feature_flagsList, view, and evaluate feature flags
write:feature_flagsCreate, update, and delete feature flags
read:deployment_zonesList and view deployment zones
write:deployment_zonesCreate, update, delete zones, and deploy releases
read:releasesList and view releases
write:releasesCreate and delete releases
read:usersList and view users
write:usersManage users
read:organizationsView organization details
write:organizationsUpdate organization settings
read:tokensList service accounts and tokens
write:tokensCreate and delete service accounts and tokens
read:webhooksList webhook endpoints and history
write:webhooksCreate, update, and delete webhook endpoints

Wildcard Scopes

ScopeDescription
read:*Read access to all modules
write:*Full access to all modules (implies read:*)

Scope Plans

When creating a token, you can select a plan to get a pre-defined set of scopes, or select individual scopes manually.

PlanIncluded ScopesUse Case
Control Planwrite:instances write:licenses write:customers write:deployment_zones write:releases write:users write:organizations write:tokensFull write access to all management resources — for administrative tools, provisioning pipelines, and internal services
Data Planread:feature_flags write:entitlementsRuntime data plane access — for your product's backend to read feature flags and report entitlement usage

Rules

  • write:X always implies read:X — you don't need both
  • A token with write:* can do everything
  • OFREP endpoints (/api/ofrep/v1/...) require read:feature_flags
  • Scopes are embedded in the JWT claims after token validation

On this page