Undoing a configuration change
Governance settings change all the time. A policy gets a new condition, a reviewer chain gets a new step, a status mapping gets a different waiting time. When one of those changes turns out to be wrong, you can take it back from the change log without rebuilding the old state by hand.
Two ways back
- Revert this change undoes one entry in the change log. The object goes back to how it was just before that change. If the same fields changed again since, RapidValue refuses and tells you which later change to revert first. It never merges two changes on its own.
- Revert to this version puts an object back, in one step, to how it was right after an earlier change. This one overwrites the changes made since, on purpose, and says how many it overwrites before you confirm. A policy or rule that was deleted since comes back under its old business id. A version in which the object did not exist yet deletes it.
Both are a new change. The original entries stay in the change log, and the new entry points at the change it reverts or the version it restores, so an auditor sees the mistake, the correction and who made both.
What you see before you confirm
The revert screen lists every field that changes, with its current and its restored value. When the change reaches people, it says who:
| What you revert | What the preview shows |
|---|---|
| An access policy or the contents of a role | Who gains access and who loses it, per system, and who keeps it through another rule or role. The safety limits judge the removals the same way as any other change. |
| An HR status mapping | The people whose HR source reports that status value today. |
| An access profile | The people who are held on that profile. |
| Governance of an account type | The people who hold an account of that type. |
The preview counts everyone and names up to 25 people. The confirm button stays disabled until the preview has loaded. A revert that would not land as shown is not applied at all: RapidValue reads the object back after the change and rolls everything back when it does not match.
What can be reverted
- Access policies, and the contents of roles.
- Approval rules, including their order, SoD rules and certification rules.
- Reviewer chains, including which chain is the default.
- Field visibility.
- Notification rules, business defaults, review settings per kind and workflow definitions. A reverted workflow becomes its next version.
- The exception policy and the MFA mode. Going back to enforced MFA needs a second factor, the same as setting it.
- HR status mappings, access profiles and account-type governance.
Switching HR source has its own way back: the Switch HR source tab on the old source's system page shows how many people move back and how many leavers return before you roll the switch back. The rollback goes through only with those same numbers.
Who may revert
A revert needs the same permission as the edit it undoes, and undoing a create needs the permission to delete. A revert adds no approval of its own: the preview is the safeguard, and the safety limits still apply.
A revert does go through the same approvals as the edit it undoes. Reverting the contents of an active role is a change to a live role, so it waits for the role's owner (or the IAM team, and the security team when it would break a separation-of-duties rule) before the role changes. See Roles and role mining. Draft roles, and roles where an administrator has switched that approval off, change at once.
Known edges
- Only changes recorded with their full before and after state can be reverted. Changes made before this was introduced, in November 2026, show as not revertible.
- The identity provider configuration and the runtime authorization mode cannot be reverted. Change them through their own settings.
- The configuration of a connected system is staged and applied instead. See Environments and configuration.
- A change made directly through the API to a system's configuration writes no change-log entry, so it cannot be reverted from there.
Further reading: