Governance & Control
Control what agents can do.
See what they did.
Set role-based permissions, define what each agent can access, and give tasks a budget for time, tokens, and cost. Keep human approvals at the decision points that matter and inspect what happened afterward.
Decision flow · exampleUse permitted context.
The pricing agent has the business material needed to prepare a recommendation for this request.
Role-based permissions
Give each role the right permissions.
Use role-based permissions to control access and responsibilities across your team. Define who can view work, change configurations, deploy team versions, approve actions, and restore a saved version according to their assigned permissions.
Set each agent’s access separately: which business context it can use, which tools it can call, and which actions need a person’s approval. Reading a procedure does not give an agent permission to take every action it describes.
Permissions and policy
Specify the scope for each step.
In a quote workflow, an agent may need the RFQ, the pricing procedure and permitted account records. Those inputs help it draft a recommendation; they do not authorize an external send.
For developers, the questions are concrete: which context can this role use, which tools can it call, and which action needs review?
Use the RFQ, pricing guidance and the account records permitted for this task.
Relevant procedure and permitted records are available to the reviewer.
Human approval
Pause at the decision point.
In the example, agents prepare a quote and the quote owner reviews it before anything is sent. Approval can advance the task to an authorized action; a request for revision sends the proposal back for work.
Temporal supports the wait and resumption in supported workflows. The person makes the decision; the agent does not gain wider authority while it waits.
Evidence after the decision
A trace is part of the record.
Built-in Langfuse helps inspect the agent run: agent and model choices, tool calls, handoffs and usage signals. That explains what happened inside the agentic system.
The business record answers a different question: who approved and what changed in the connected system. For an audit or incident review, examine both and any other evidence your organization requires.
Use the trace to inspect agent behavior and investigate a run.
Task budgets
Keep work within your budget.
Set a time, token, or cost budget for a task. Corin can plan the agent team and its coordination around that constraint, with signals as the budget approaches its limit.
Track time, token use, and model cost across participating agents so you can see where resources go and review changes against the budget.
Build with Corin
Try a task with an approval point.
Start with a useful example. Identify the context and actions in scope, then choose where a person reviews the proposed action.