The review requests (also 4-eyes principle) is a control where one person makes a change and a different person must review and approve it before it takes effect. We support this for three areas of the product - scenarios, query templates and custom list records. Each is switched on separately, so you choose exactly which parts of the platform get the extra layer of control.
How the review cycle works
A user (the submitter) makes a change — for example, activates a scenario, edits a query template, or adds a record to a custom list.
A new review request is created instead of applying the change outright, and shows it as pending.
Any other user with review permission (the reviewer) opens the change from the Review Requests page, or from the item itself, and approves, rejects, or leaves it as is. The submitter can withdraw their own request instead of waiting for a reviewer.
Approving applies the change. Rejecting or withdrawing discards it — nothing changes.
It is enforced that the reviewer is not the submitter. A user can never approve or reject their own change; the only action available on your own request is to withdraw it.
Where it's available today
Area | What requires a second approval |
Query templates | Creating, editing, or deleting a query template |
Scenarios | Activating or deactivating a scenario |
Scenario versions | Making a new version current |
Custom list records | Adding, editing, or deleting a record |
These are three independent toggles — you can have a 4-eyes enabled for query templates without turning it on for scenarios or custom lists, and vice versa.
Who can approve
By default, the following roles can review and resolve requests: Customer Admin, Customer Agent, and Analyst.
Where to find pending items
Go to Review Requests in the main navigation to see everything awaiting approval across every area you have enabled, who submitted it, and when. From there, open an item to approve, reject, or — if you submitted it yourself — withdraw it.
