Configuration revisions and rollback

Every location’s configuration — routing rules, cadence and caps, consent and quiet-hours rules, disposition list, notification policy, and export mapping — lives in a numbered revision with a content hash. Changing it means creating a new revision, approving it, passing readiness checks, and activating it. Each step is separate and each step is logged. If the new revision misbehaves, you roll back.

What you’ll see

The Location configuration card shows the active revision, for example “Revision 14” with “Approved” and “Active” chips, a line “content sha256 · 9f3a…e1c4”, and who did what: “Approved by R. Okafor · activated by admin”. Four buttons follow: Preview, Approve, Activate, Roll back. Buttons that do not apply to the current state are disabled.

The Readiness checks panel lists what must pass before activation:

• Locations mapped · 4 of 4
• Roles and scopes assigned · 6 roles
• Consent and quiet-hours rules · Valid
• Disposition list · 6 entries

Steps

1. Create a draft revision and make your changes. The draft gets the next number and a new content hash.
2. Click Preview to see the effective rules side by side with the active revision.
3. Have a second admin or manager click Approve. Approval is separate from authorship.
4. Confirm every readiness check reads as passing. A failing check disables Activate.
5. Click Activate. The ledger records config.activated · rev 15 with actor “admin” and scope “organization” or the location.
6. Watch the queue for the first hour. Cadence, routing, and notification changes apply to work created after activation.

Rolling back

1. Open the Location configuration card and click Roll back.
2. Choose the previous approved revision. Its hash is shown so you can confirm it is the one you expect.
3. Confirm. Rollback is its own logged event, not a deletion. Revision numbers keep counting upward.

If something looks wrong

• Activate is disabled. A readiness check is failing or approval is missing. Read the panel.
• The hash changed after approval. Someone edited the draft. It needs approval again.
• Agents still see old behaviour. Items in flight keep their reserved attempt and cadence. New items use the active revision.

Related

• Roles and scopes
• Reading the audit ledger
• Retry cadence by location