What approval mappings do
Approval mappings power Coordination Autopilot.
They answer:
- who should review Finance changes
- who should review Stripe changes
- who should review Pricing changes
Common mapping examples
- Domain: Finance → Finance Reviewer
- System: Stripe → Billing Owner
- Change Type: Pricing → Revenue Leadership
Why this matters
Without mappings, coordination remains manual.
With mappings, the system can automatically suggest the correct reviewers when a change is created or updated.
Approval mappings
Mappings Table
Recommended mapping strategy
Start with:
- domain mappings
- critical system mappings
- high-risk change type mappings
Then expand after the first few live workflows.
Validation tips
Before relying on mappings in production-like workflows, confirm:
- each mapped role has members
- the members actually have domain review permission where required
- your most common change types resolve to the expected reviewers