Managing secrets
Two kinds of credentials power the invoice workflow:
- AI provider keys — the key the extraction agent uses to talk to the model (OpenAI, Anthropic, Google, and so on).
- Connector credentials — the API token the ERP connector uses to query purchase orders, the credentials the ledger uses to post invoices, and so on.
Superprocess keeps both as secrets at the organization level — written once, referenced by name, and never exposed in process configuration or logs.
The secrets page
Section titled “The secrets page”At Settings → Secrets (in the organization) you’ll find your secrets — each with its name, type, and what uses it, but never the value. It has an AI Providers area for model keys and a custom secrets area for everything else.
Add an AI provider key
Section titled “Add an AI provider key”On the AI Providers tab, pick the provider (OpenAI, Anthropic, Google, …) and paste the key. Save, and the platform stores it encrypted. From now on the agent’s model configuration references this key by name; rotate it here and every agent picks up the new value on its next call.
Add a connector credential
Section titled “Add a connector credential”When you set up the ERP — Purchase Orders connector earlier, its credential was stored as a secret and referenced by name — you’ll see it here. Every external system the platform talks to gets its own secret; a common convention is one per system per environment (erp-prod, erp-staging).
Rotating a secret
Section titled “Rotating a secret”Open a secret and update its value. The change takes effect immediately for every agent or connector that references it — no redeploy. If you need a grace period (the old key must keep working for an hour), leave the old credential active at the provider until the cutover is done.
Who can see what
Section titled “Who can see what”| Action | Who can do it |
|---|---|
| List secrets (names and metadata) | Organization members |
| Read a secret’s value | No one — values are never exposed through the UI or API |
| Add, rotate, or delete a secret | Organization owner or admin |
The “no one can read the value” rule has one exception: the runtime, when an agent or connector makes a call, resolves the value in-process. It never leaks to logs, the UI, or the audit trail — the trail records that a secret was used, never what it was.