Approve, reject or activate a configuration change request
Change requests follow four-eyes governance: someone other than the proposer approves, then the approved request is activated to change the live value (a new version is recorded).
Have questions or need step-by-step guidance on this topic?
Step-by-Step Procedure
Open the tab
On "General Settings" click "Change Requests (n)". Each row shows the request ID and target key, the proposed value, the status, the proposer and the reason.
Approve or reject
For a PROPOSED request click "Approve" or "Reject". An ordinary proposer cannot approve their own request; the server answers "Four-Eyes Violation: Proposer cannot approve their own change request." Exception: the Super Administrator may approve their own submission with "Approve (self-approve as super admin)" after a confirmation; the approval is marked SELF_APPROVED_BY_SUPER_ADMIN and written to the audit ledger (Admin > Audit > Four-Eyes Control).
Activate
For an APPROVED request click "Activate Live". The configuration value is updated, its version number increases and a version snapshot is stored.
Confirm
The banner reads "Change Request <ACTION> successful." and an activated request shows "Enforced". Check the new "Active Value" and version on the "Configuration Registry" tab.
The request moves PROPOSED → APPROVED → ACTIVATED (or REJECTED) and, once activated, the live configuration value and version change.
Troubleshooting & Failure Modes
Was this guide helpful?
Help us refine our platform documentation