Route human review
Decide who can review a case and who receives it if the first route is unavailable. Start with organization defaults. Add an application override only when that application needs a narrower set of eligible reviewers.
Set the organization default
Choose eligible reviewers
Choose the reviewer group whose members have permission to inspect the evidence and record a decision. A shared mailbox or notification address does not make someone eligible.
Set the due time
Set a due time that gives the reviewer enough time to examine the evidence. Working hours and calendars determine when the timer runs.
Set delegation and escalation
Delegation lets another eligible reviewer claim the work. Escalation moves unclaimed or overdue work to the configured fallback. Neither action creates a second final approval.
Confirm the fallback
Choose an eligible fallback for cases the primary route cannot accept. Check that the fallback can access the application’s evidence and record the required decision.
Add an application override
Confirm the selected application and environment before adding an override. Check its eligible reviewers and fallback again after saving. Other applications continue to use the organization default.
Understand claim and decision ownership
A person or eligible group receives the case, then one eligible reviewer claims it. To claim, a reviewer needs a role that can review this application and, when the case needs a final decision, can record one. In VeriProof that must be the role you’re using, so switch roles first if your current one can only review. When you claim from a Teams group post, VeriProof uses whichever of your roles qualifies. The reviewer who records the final decision is written to the audit history. Notifications can point people to the Inbox, but the Inbox remains the source of truth.
When an Administrator turns on separation of duties, routing leaves out an application’s owners. If no one else is eligible, the review still reaches an owner, who must confirm before deciding.
When Slack is connected, you can post an application’s group reviews in one private Slack channel. An eligible reviewer claims from the post’s Claim review button, or Claim in VeriProof while decisions in Slack are off, and then decides in their own direct message. Post group reviews in a private channel covers the setup.
When Microsoft Teams is connected, you can post an application’s group reviews in one Teams channel instead. Every member must be an internal member of your connected Microsoft Entra tenant. Eligible reviewers claim from the post, and the reviewer who claims it can decide there when decisions in Teams are on. Post group reviews in a team channel covers the setup.
An email address does not grant reviewer permission. The recipient must sign in and be eligible before viewing evidence or recording a decision.
Advanced approval chains, parallel approvals, voting, and threshold approvals are not available in this release.