Approvals
CAB decisions on changes, service-request approval steps, quorum rules, and the separation-of-duties floor under all of it.
Change approval — the CAB
Every change is decided in its decision docket. When a decision opens, the docket freezes the electorate (the approver roles, including through groups, minus the requester), the decision rule, the threshold, the veto holders and the timeout, so later role changes or edits cannot move the result. The change policy selects one of four decision rules:
| Decision rule | How it decides |
|---|---|
| Single approver | One approval decides. |
| All approvers required | Every seat must approve; veto is on, and an abstention keeps the seat. |
| Majority with quorum | At least two approvals. |
| Staged: technical, then business | Change approvers decide the technical stage, then service owners the business stage. |
The tenant minimum number of approvers can raise the floor, never lower it. The policy's approval rules can route changes by risk band, type, service or CI class to a rule, and can optionally approve low-risk Normal changes automatically. A Standard change on an eligible pre-approved template is authorised by the template, with no CAB vote; an Emergency change is implemented first and decided retrospectively. See Approval and the CAB for the full picture.
Approval mechanics worth knowing:
- Reject short-circuits. A reject or a veto ends the change as Rejected; approvals collected so far do not outvote it.
- The implementer cannot be the only approver. This is checked by person when implementation starts, because the implementer can change after approval. While only the implementer has approved, the docket shows the gap explicitly and implementation cannot start.
- Stalled decisions are overridden, not approved. A change manager can force an outcome with a reason; it is recorded as overridden, never as approved, and is refused under Single approver.
Service-request approvals
Approval for service requests is configured per catalog item, not globally. A request model declares ordered approval steps, each with an approver role and a quorum (default 1). A model either requires approval (and must define steps) or doesn't (and must not) — there is no ambiguous middle state. Requests against a no-approval model skip straight to fulfillment.
Approvers see their pending votes in My work and in the approvals queue; the queue is role-scoped, so two approvers with different roles see different lists.
Quorum rules
These quorum rules apply to approval steps outside the change decision docket; changes use the decision rules above. A policy's quorum rule — any, majority, all, or first responder — describes how the required count relates to the eligible approver pool. The enforced floor is always min approvers; majority and all can raise the effective requirement further when more eligible approvers exist.
Separation of duties — beneath configuration
Whatever you configure, these hold, because they are enforced in the domain layer, not in settings:
- The requester of a change cannot approve or reject it.
- The implementer cannot be the sole effective approver.
- A service-request approver cannot approve their own request.
Dual-approval flows
Beyond records, four-eyes approval guards the platform's most sensitive operations: switching off a sticky regulatory feature flag, de-pseudonymizing a user's data, and granting sensitive role assignments (which expire after 14 days if not decided). Each is its own explicit request-and-approve surface with a full audit trail — see why regulatory toggles are sticky.