Skip to Content
Configure VeriProofHuman review and escalation

Human review and escalation

Use this page to find incomplete setup or review work that needs attention. Start with organization defaults for reviewer routing and timing. Then select an application to check its human input profiles, callbacks, and SDK connection.

Read the Core Human Review lifecycle guide before publishing an interaction profile or enabling an application callback.

Check readiness

Review organization defaults

Confirm that an eligible reviewer can receive the case and record the final decision. Review the working calendar, escalation timing, and retention checks.

Decide whether application owners can review their own applications

Under Separation of duties, turn on Require a different reviewer for application owners and select Save setting. Only an Administrator can change it. It applies to every application in the organization. See Separation of duties for what changes.

Choose an application

Switch to Application setup, then choose the application and environment you want to check.

Finish application setup

Create a human input profile when reviewers need to return typed values. Keep it to 12 fields, preview what the reviewer will see, and validate the draft. Before publishing and activating the version, confirm what reviewers must return and what the application may do with that response.

Then complete the callback address, safe test, and SDK connection shown for the selected application. The page checks the current setup and shows the next action that still needs attention.

There’s no callback secret to create or store. VeriProof signs every callback with its own keys, and your application checks the signature against the public keys published at /.well-known/veriproof-webhook-keys.json on your VeriProof API. The VeriProof SDK receiver does this for you. See How VeriProof signs requests if you verify callbacks in your own code.

Post group reviews in Slack or Teams

If the application’s reviews go to a group and Slack is connected, its reviewer routing shows Slack channel for group reviews. Choose a private channel to post each group review once instead of messaging everyone in the group. The list shows only private channels that you and the VeriProof app are both in, so connect your own Slack account first. See Post group reviews in a private channel.

If Microsoft Teams is connected, the reviewer routing also shows Microsoft Teams channel for group reviews. Choose a channel, select Check channel, confirm what members will see, and select Save channel. See Post group reviews in a team channel.

Change a profile without changing open work

Use Replace profile to change fields, safe context, permitted replacements, or what the response allows the application to do. Activating the next version replaces the active version for new cases. Open reviews keep the profile and request snapshot they started with.

Open work that needs attention

Choose a health card to open the exact filtered records behind its count. Choose Diagnostics and repair when you need the existing review or application side panel.

Separation of duties

The setting is off by default, so anyone with review authority for an application can decide its reviews, including its owners. When you turn it on:

  • Routing sends an application’s reviews to eligible reviewers who don’t own it.
  • If an owner tries to decide anyway, through a manual assignment, a review assigned before the setting changed, Slack, or Microsoft Teams, VeriProof refuses the decision while someone else can decide. The owner sees why and can ask a review coordinator to reassign it.
  • “Someone else” means an active person who isn’t an owner, holds a current role with the same review authority, and can access the application.

Small teams

A solo or very small team may have no one but the owner who can decide. Reviews still reach the owner. In VeriProof, the owner sees Confirm and record and must confirm they’re deciding as the only eligible reviewer. The decision then records that separation of duties wasn’t possible, so the record stays accurate. Slack and Teams can’t collect this confirmation, so they send the owner to VeriProof to decide.

Confirmation doesn’t override the rule: if anyone else can decide, the owner’s decision is still refused.

A callback is not ready until its safe test succeeds and you confirm its retention and security choices. Opening a repair view does not change records.

Advanced integration chains and multi-stage approval patterns are not available in this release.