Delegated authority
Authority Register
Autonomy is only safe if somebody wrote down what each agent and each person is allowed to decide. This register is that document, and it is enforced: the decision route resolves a grant before it writes anything, and refuses when nothing covers the action.
Health
What the estate is currently allowed to do
Grants in force, who holds them, how often they are used and how often they are exceeded.
GB8-AUTH-A1
Master Data Orchestrator · AI GBS & Global Business Services · Master Data Management
Any unit on a master data management line where every intake check passed, the policy in force is current, and the value sits inside the cap below.
- Confidence at or above the line threshold, otherwise the unit is held.
- Policy version in force must be current, not superseded.
- Every action writes to the evidence spine before the unit advances.
11 grants
Select any row to see the conditions, the delegation chain and how it has been used
| Reference | Holder | Decision type | Cap | Jurisdictions | Delegated from | Expires | Uses 30d | Status |
|---|---|---|---|---|---|---|---|---|
| GB3-AUTH-A1 O2C Control Tower | Order-to-Cash Tower Orchestrator orchestrator | Clear and route work on the o2c control tower lines | $2,000k | US UK DE | Tower Lead, Order-to-Cash | 2027-05-16 | 2789 | Active |
| GB5-AUTH-A1 Service Catalog & Intake | Catalog & Intake Orchestrator orchestrator | Clear and route work on the service catalog & intake lines | $2,000k | US UK DE SG | Head of Service Catalog | 2027-01-15 | 3614 | Active |
| GB4-AUTH-A1 R2R Control Tower | Record-to-Report Tower Orchestrator orchestrator | Clear and route work on the r2r control tower lines | $2,000k | US UK DE SG AU FR | Tower Lead, Record-to-Report | 2027-01-24 | 346 | Active |
| GB8-AUTH-A1 Master Data Management | Master Data Orchestrator orchestrator | Clear and route work on the master data management lines | $2,000k | US UK DE SG AU FR BR | Head of Master Data | 2027-03-16 | 3844 | Active |
| GB1-AUTH-A1 H2R Control Tower | Hire-to-Retire Tower Orchestrator orchestrator | Clear and route work on the h2r control tower lines | $2,000k | US UK DE | Tower Lead, Hire-to-Retire | 2026-10-21 | 1201 | Active |
| GB6-AUTH-A1 Global Process Ownership | Process Ownership Orchestrator orchestrator | Clear and route work on the global process ownership lines | $25k | US UK DE SG AU FR BR | Global Process Owner | 2026-12-18 | 765 | Active |
| GB7-AUTH-A1 Automation Factory | Automation Factory Orchestrator orchestrator | Clear and route work on the automation factory lines | $250k | US UK DE | Head of Automation | 2027-05-22 | 4101 | Active |
| GB10-AUTH-A1 Continuous Improvement | Continuous Improvement Orchestrator orchestrator | Clear and route work on the continuous improvement lines | $250k | US UK DE SG | Head of Continuous Improvement | 2026-11-23 | 277 | Active |
| GB2-AUTH-A1 S2P Control Tower | Source-to-Pay Tower Orchestrator orchestrator | Clear and route work on the s2p control tower lines | $2,000k | US UK DE SG AU FR | Tower Lead, Source-to-Pay | 2027-05-06 | 3279 | Active |
| GB11-AUTH-A1 Cost-to-Serve Management | Cost-to-Serve Orchestrator orchestrator | Clear and route work on the cost-to-serve management lines | $2,000k | US UK DE | Head of Service Economics | 2027-04-21 | 2257 | Active |
| GB9-AUTH-A1 Service Delivery Management | Service Delivery Orchestrator orchestrator | Clear and route work on the service delivery management lines | $250k | US UK DE SG | Head of Service Delivery | 2027-05-09 | 1047 | Active |
How the register is enforced
Not a wall chart
When a decision is recorded, the route resolves a grant first: the right function, the right holder kind, an active status, a cap at or above the value at stake, and the jurisdiction of the work. If no grant covers all five, the route returns a refusal and writes a refusal record into the evidence spine. The decision does not happen.
Refusals are evidence in their own right. A cap breach that was stopped is worth more to an examiner than a clean run, because it shows the control fires.
Expiry is a real state, not a label. An expired grant authorizes nothing, which is why the sixty-day expiry tile matters more than the active count.
What is still missing
Say it before an examiner does
The holder identity on a grant is a name, not a cryptographic identity. Nothing here proves the actor was the actor. Signed agent identity and attestation are separate work and are not built.
The persona a user is browsing under is chosen in the interface and is not yet an identity the server trusts. The register is enforced against the value and the function; it is not yet enforced against a verified caller.
Delegation is one hop deep. A real board delegation chain runs several levels, with sub-delegation rules and counter-signatures. That depth is modeled as a single delegated-from field here.
Actions
What is waiting on a person
A grant is a written permission with an expiry, a cap and a named delegator. Nothing below renews itself.
Renew or let a grant lapse
Expires within ninety days. On expiry the holder falls back to asking.
Explain a grant that was exceeded
148 attempts beyond the cap in the last thirty days across these grants.
Withdraw a permission nobody uses
Granted and never exercised. Unused authority is still authority.
Nothing else is pending
Every other grant is inside its cap and inside its term.
Operations
What this desk is allowed to start
A surface that only reports is not operable. This is the work this page can set in motion, and the bound it runs into.
Trigger and bound
This desk can grant, narrow, extend or revoke a permission, and every one of those is written to the spine with the person who did it. It cannot let a holder act above the materiality cap on the grant: an attempt above the cap is refused at the point of decision and recorded as a breach rather than allowed and flagged afterwards.
Live observability
What the record shows right now
Grants split almost evenly between agents and people. 352,403 uses in the last thirty days produced 148 attempts above cap.
Current distribution
309 grants
Is policy and strategy coming to fruition
Whether the written intent is holding here
148 cap breaches against 352,403 uses — 0% of exercised authority went past its bound.
Not holding on the record
The policy position is that no actor, agent or human, may commit the company past a stated value without a named delegator standing behind it. The record shows 309 active grants and 148 attempts above cap in thirty days, every one refused at the point of decision rather than allowed and reported later. That is the intent working. The part that is not proven is the ceiling itself: the caps were set by this team, not benchmarked against loss experience, so a grant being inside its cap says the rule held, not that the rule is right.