Auth and Access
Authentication
Every authenticated Scriptum call carries a bearer token:
Authorization: Bearer <token>
Your organization context travels with the request — the dodil CLI and the gateway attach it, so you don’t manage it by hand. All script, thread, and env data is isolated per organization: you only ever see your own.
A few read-only operations need no auth — HealthCheck and the template reads (ListTemplates, GetTemplate).
Authorization (scopes)
Access is enforced per RPC: each method maps to a named scope — creating a script, publishing a draft, running a thread, reading env, and so on. Tokens issued to your organization carry the scopes they’re entitled to, and a call missing the required scope is rejected. Scopes line up one-to-one with the operations in the API Reference.
Environment variables and secrets
Scriptum stores per-org configuration in the env store — tenant-level keys plus an optional per-script overlay. Treat these as sensitive:
Security note.
ListEnvVarscurrently returns stored values, not just keys — so anyone who can list env for your organization can read those values. Restrict who holds env-listing access, and keep anything you’d rather not expose in plaintext out of env where you can.
Not yet available
A few operations are defined in the API but not implemented yet (see Feature Status): thread cancellation (CancelThread) and artifact listing (ListArtifacts).