Help Center/Admin Operations/Propose, approve and activate a policy change
Admin Operations•Last updated: 2026-10-20•3 min read

Propose, approve and activate a policy change

Policies lists configuration records, business rules and change requests. A value changes only through a change request: a super administrator proposes it, a different super administrator approves it, then it is activated and a new version is stored.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Open the page

Open "Platform Configuration" and click "Policies" (address /admin/config/policies). Rows have a "Kind": Change request, Configuration or Business rule, with "Value", "Version", "Status" and a "Note". Secret values show "hidden (secret)".

2

Propose

Click "New Record". Choose "What to change" (Configuration value or Business rule parameters), enter the "Key" exactly as in the table, the "Proposed value" (a number, true/false, text or JSON) and a "Reason", then save. The request is recorded with a real validation of type and declared bounds; the message tells you if validation failed.

3

Approve

A second super administrator selects the Change request row and clicks "Approve". An ordinary administrator cannot approve their own request: the platform refuses with a four-eyes message. 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).

4

Activate

Click "Activate" on the approved request. The live value changes and a new version is stored. "Reject" closes a request that is still open.

Expected Operational Outcome

The setting has its new value, the change request shows ACTIVATED and the version number went up; everything is recorded in the audit trail.

Troubleshooting & Failure Modes

Symptom: "No global configuration with the key ... exists"
Likely Cause: The key is wrong or the setting has only a non-global scope.
Resolution: Copy the key from the table.
Symptom: "Four-Eyes Violation"
Likely Cause: You proposed this request and are not signed in as the Super Administrator (or used a machine key).
Resolution: Ask another administrator to approve it, or sign in as the Super Administrator and use "Approve (self-approve as super admin)".

Was this guide helpful?

Help us refine our platform documentation