Approvals
3 min read
Approvals let you decide how independently an agent can work. When an action requires review, Kujira holds it before execution and shows it in the Approvals queue.
Open Approvals in KujiraDefine the degree of autonomy
In every agent's configuration, the proactivity system divides actions by the impact the agent estimates, from 0 to 100. The initial values are 70 to ask and 90 to block, but you can adapt them to each role.
0 – 70Actúa sin aprobación. Trabajo rutinario y reversible.
70 – 90Pide permiso; si no respondes, continúa con su propuesta.
90 – 100Espera una decisión humana antes de continuar.
The estimate depends on the model
An action's score is not a fixed classification: the agent itself estimates its impact before acting. It also decides whether an action belongs to an Always ask category. Use approvals as a supervision layer based on its reasoning; to block a capability deterministically, disable it in Behaviour.
You also set the middle band's timeout per agent. Use it to keep work flowing for reversible decisions; blocking actions do not expire or run until a person resolves them.
Actions that must always be reviewed
Alongside thresholds, Always ask lets you define categories that require approval regardless of the level the agent estimates. It is the right protection when the type of action matters more than its specific context.
Start from the configuration suggestions and tailor them to your case:
- Spending money or accepting a cost.
- Deleting or overwriting data.
- Sending external communications or publishing content.
- Installing tools or modifying infrastructure.
- Sharing credentials.
- Making commitments to third parties.
An approval authorizes only the specific decision presented. It does not make a similar action permanently allowed.
What the decision maker receives
Each request includes a title, a summary of what would change, and the impact identified by the agent. When it needs more context, it can attach details so you can review the plan before responding.
The agent requests a decision
You review and decide
Kujira delivers the result
For middle-band judgement requests, the agent can suggest a fallback option. If nobody responds before the timeout, that option is applied; if no safe option exists, the question expires and the agent decides with the information available. Blocking questions always wait for a person.
Who can resolve them
To approve, reject, or answer a request, you need the permission. View permission lets you see the queue, but not decide for the organization.
| Action | Permission |
|---|---|
| View the approval queue | approval.view |
| Approve, reject, or answer a request | approval.resolve |
The first valid decision resolves the request. Its result is reflected in the queue and delivered to the agent once, even if several people were reviewing it simultaneously.
Approval and capability are separate controls
An approval reviews an action the agent can attempt. To prevent it entirely, disable the corresponding capability in Behaviour. For example, blocking the credential capability prevents its use; requiring approval lets it be requested case by case.
Design a practical policy
Start by letting the agent resolve routine work, and use mandatory rules for anything with external, financial, or irreversible impact. If a queue builds up too many decisions, reduce mandatory categories or raise the ask threshold; if the agent takes unnecessary risks, do the opposite.
Also review Notifications to ensure pending requests reach the right people.