Feature Flags

Feature Flags control the rollout of functionality within an enabled capability. They are not a licensing mechanism — that's Capability SKUs.

Read your feature flags#

Feature flags are returned alongside capabilities:

curl "https://your-company.authspoke.com/api/v1/platform/capabilities" -H "Authorization: Bearer $TOKEN"

{
  "features": {
    "RELATIONSHIP_GRAPH": true,
    "AI_ASSISTANT": true,
    "POLICY_SIMULATOR": false,
    "AUTONOMOUS_DISCOVERY": false,
    "AGENT_TRUST_SCORING": true,
    "RISK_RECOMMENDATIONS": true
  }
}

What flags gate#

A flag, when off, should make the feature behave as though it does not exist — across UI visibility, API availability and background processing. For example, AI_ASSISTANT controls whether the "Ask AuthSpoke" experience appears, and RELATIONSHIP_GRAPH gates the relationships view.

Managing flags#

Like SKUs, toggling a flag is a provider-only operation performed per tenant from the Provider Console. Clients only read flags via /platform/capabilities.

Use them in your client#

Read the flags once after sign-in and branch your UI accordingly — never hard-code a feature's availability. Because the same endpoint backs every client, your SDK, CLI and UI stay consistent.