Skip to main content
DataRaven uses a layered permissions model. Every request is authorized by checking two things:
  1. User Role — hierarchical team membership role (JWT sessions)
  2. API Key Scope — granular scope string (API key authentication)
A request succeeds when the caller meets at least the minimum role shown below, or presents an API key that includes the listed scope.
Some actions are JWT-only — they cannot be performed with an API key. These are marked with a in the API Key Scope column.

Role Hierarchy

Roles are hierarchical — higher roles inherit all permissions of lower roles.

Locations

Secrets

Tasks

Executions

Vault Connections

Notifications

Audit Logs

Teams

Team management actions (create, update, delete, member management) are JWT-only. API keys cannot create or modify teams.

Invitations

All invitation actions are JWT-only. User-scoped endpoints (get/accept/decline) require only a valid session — no team role is needed.

API Keys

API key management is JWT-only. You cannot use an API key to create, revoke, or rotate other API keys.

Subscriptions & Billing

Usage


Scope Reference

API key scopes follow the resource:action pattern. Here is the full list of available scopes: