---
url: /handbook/governance/approval-chain.md
description: >-
  The people who approve human access decide on agent access. Three decisions,
  every step.
---

# Approval chain

DutyGraph routes each agent request through the same people who approve human access. The default chain is:

1. **Manager**: is this the owner's work, and do they need this agent for it?
2. **Role owner**: does the work need this access in the systems they own?
3. **Internal Controls**: checks segregation of duties (SoD) and may tag a mitigating control.
4. **IAM**: records the issue in DutyGraph.

Each label uses the company's own terms.

## What each approval means

Today, judging whether each scope is needed is the reviewers' job. The evaluator does not check scopes against the Task Cards (rule CEIL-02 is not enforced). See [The key join](the-key-join.md).

A manager confirming that the work exists is not IAM approving privileged access. Each step records its own decision.

## Exactly three decisions

Every step has the same three decisions:

| Decision | Rule |
| --- | --- |
| **Approve as proposed** | Never disabled. A checklist shows what is still open. |
| **Approve with changes** | A change can only narrow access ("send back with less"). |
| **Deny** | Needs a reason. |

## What the chain enforces

* **The requester never decides.** The requester's view has no decision control, not even a disabled one.
* **One person, one step.** A person may decide only one step of a request. The owner cannot hold a step of their own request.
* **No departed approvers.** A step assigned to a person who has left cannot start. Change the chain first.
* **Chat never decides.** No MCP server has a decision tool. Decision routes refuse calls that come from MCP.
* **Context is pinned.** The server checks the step's assignee and the request's context fingerprint. If the request, the access export or the rules changed, the decision is refused.
* **The ceiling is rechecked.** An approval and the issue step check that the owner still holds each remaining scope.
* **An open SoD conflict needs a control.** Only a step that may tag controls can approve it, and only with a control that covers agents.

## Approval is not provisioning

When IAM issues, DutyGraph records the decision on the [ledger](ledger.md) and creates a credential for the DutyGraph gateway. It does not create an identity or grant access in any business system. The "For IAM to do" card tells IAM what to provision in the company's own systems. See [Approval, provisioning and revalidation](approval-provisioning-and-revalidation.md).

::: info
**Status.** **Built**: the chain, the three decisions and the checks above. **Simulated**: in the sample companies, approvers are sample personas the advisor operates. **Planned**: signing in through the company's SSO, and sending the approved decision to the company's IAM.
:::
