Automation identities
Scoped non-human identities for recurring Growth and Revenue routines and external agents.
Automation (/app/automation, admins) creates explicitly scoped non-human identities for recurring Growth and Revenue routines and external agents — without sharing credentials to your specialist systems.
Creating an identity
Give it a name (for example Daily Revenue Operator) and a description, then set its authority:
| Setting | What it limits |
|---|---|
| External actions per day | How many actions with external effects it may take. |
| Spend ceiling per day | Maximum paid-media spend changes, in one currency per identity and day. |
| Eligible communications per day | How many messages it may send. |
| Credential expiry | Days until the credential expires. |
| Allowed agent IDs | Optional list of internal agents it may bind to. |
| Operating window | Optional local-time hours; outside them it cannot start or continue actions. |
| Data scope | No business data (default), or one organization unit. |
| Allowed business reads | The specific business context it may read, for example Revenue customers. Data scope and capability scope are independent. |
The secret
When an identity is created, its secret is shown once. Copy it immediately — Blocchi does not store or show the plaintext again. Editing an identity's authority later does not require rotating the credential.
Governance
Automation identities use the same governed action runtime as people: permissions, source policy, confirmation or approval, idempotency and audit. Limits are enforced on the server.
Related
Last updated on