Review a configuration change
What this achieves
Section titled “What this achieves”Some configuration changes are held until a second administrator reviews them, so no single person can change a setting and apply it unseen. This screen is where those changes wait.
Required role: Administrator.
- Go to Approvals → Configuration Approvals.
- Stay on the Pending tab.
- Read the change: its type, the description of what is being changed, and who requested it.
- Open View change diff to see the values before and after.
- Select Approve or Reject.
- Add Review notes. They are optional, and they are what the requester gets back.
What a pending change shows you
Section titled “What a pending change shows you”| Option | Description |
|---|---|
| Type | The kind of configuration being changed. |
| Description | What the requester says the change does. |
| Requested by | Who raised it, and when. |
| View change diff | The values as they are and as they would be. |
Read the difference, not the description. The description is what the requester believed they were changing; the difference is what would actually change.
Example: Priya Raman requests a change to a payroll setting at HC Corp and describes it as a correction. Daniel Okonkwo opens the difference, sees that it also alters a second value nobody mentioned, and rejects it with a note asking for the two to be raised separately.
Reviewing history
Section titled “Reviewing history”The All tab lists every configuration change with its status — pending, approved, or rejected — and shows who reviewed each one, when, and the notes they left. Filter by status to find a change somebody says they submitted.
Why this exists separately from approval routes
Section titled “Why this exists separately from approval routes”This is a control on the system’s own settings, not on employees’ requests. It sits apart from workflow routes because it protects a different thing: the configuration that everything else depends on.
The principle is the same one that runs through the rest of the product. Whoever makes a change is not the person who confirms it.
What happens next
Section titled “What happens next”An approved change is applied and both the request and the review are recorded against the people involved. A rejected change is not applied, and the requester has your notes to work from. Either way the outcome appears in the audit trail with the rest of the record.
Related
Section titled “Related”© 2025-2026 Humavera Documentation - BPilot Ltd. All Rights Reserved