ServiceNow sandbox

The ServiceNow integration is under validation. It is not yet available for general use. The first workflow uses a dedicated sandbox connection, native ServiceNow tickets, and a small companion app.

Review an application action

The sandbox review experience follows the same rules as VeriProof review in Teams and Slack:

1. VeriProof sends review work to the assigned ServiceNow ticket.
2. The reviewer selects Review request on that ticket.
3. If needed, the reviewer links their ServiceNow account to their own signed-in VeriProof account.
4. The dialog shows the current request, its closing time, and the responses the person is allowed to give.
5. The reviewer supplies any required reason, confirmation, or information and submits the response.

Use your own ServiceNow account and your own VeriProof account when linking. Reopen the ticket’s review after the link is confirmed.

To disconnect your own review account, open Personal settings from your avatar menu in VeriProof. Under ServiceNow account, Connected shows that your account is connected. Select Disconnect account and confirm to disconnect it. Reconnect from Review request on an assigned ticket when needed. Connecting does not grant review permission.

The account section appears for approved ServiceNow reviewers with application review access and a usable organization review-work connection. It also appears for anyone already connected to the current organization connection, so they can disconnect their own account. It is hidden in demo and role preview. This does not make the sandbox integration available to every organization. An open ServiceNow form must pass the current account-link check before it can record a decision.

VeriProof checks identity, current access, assignment, and the displayed request before recording the decision. A changed request must be reopened. Some forms require the VeriProof portal; follow the link to the same review.

Choose Respond when the request asks you to provide details, then complete the required fields. Forms can include choices, checkboxes, numbers, amounts, percentages, dates, short answers, and longer responses. Complete these fields in the ServiceNow dialog. Required fields are marked, and messages beside a field explain what to correct. When Ask a question is offered, use it to request more information. Your question goes to the application and leaves the protected action waiting. Approval-only requests offer Approve and Reject. They do not accept follow-up questions.

A recorded decision and the application’s result are separate events. Approval can permit the application to continue; it does not prove that the action ran. The application must report its result. Closing, assigning, or editing the ServiceNow ticket does not record a VeriProof decision.

The Ticket’s due date follows the review’s work deadline. The closing time in the dialog is when the review expires. Change the review owner in VeriProof to update the Ticket’s assignment. An owner without an approved ServiceNow account leaves the Ticket unassigned.

Check work delivery

Administrators can inspect Review work delivery in the ServiceNow settings. The list shows VeriProof’s saved delivery status, with unresolved work first.

When a delivery needs attention, inspect the original operation in ServiceNow. Use Check delivery after resolving the cause. The existing delivery job checks that operation’s receipt. Refresh the status after the job runs. This check does not create another ticket or record a human decision. If the receipt still cannot be confirmed, delivery remains paused for investigation.

If someone changed the Ticket’s managed assignment or due date, the next push stops for attention. An administrator checks that change before delivery can continue. Check delivery does not undo native edits or restart an incomplete write.

Send evidence

An administrator configures the approved instance and dedicated OAuth connection. Use a ticket created by this connection as the receiving record. The initial report is the governance summary for the selected applications.

Preview the PDF and its destination before sending it. VeriProof checks the returned attachment against the saved PDF. If delivery cannot be confirmed, retain the existing report and inspect its delivery status before starting another send. The ServiceNow recipient completes any review required by their organization.

The report follows the shared delivery schedule: significant governance changes or a due refresh can make it ready to send. Activity counts can change without making another delivery due. You can still preview and download the current report when Send report is unavailable.

A pending delivery must be resolved before another version of that report can be prepared for the same destination. A receipt check verifies the original operation; it does not upload another copy. Renaming an attachment or closing its ticket does not confirm delivery.

Scope and availability

VeriProof pushes work and evidence. It does not import ServiceNow tasks or run a ServiceNow discovery feed. Human review sends an explicit, authenticated response back to VeriProof. Delivery verification checks only the record and attachment associated with that operation.

The sandbox baseline does not require AI Control Tower, Integrated Risk Management, or Integration Hub. Those are separate product areas and are outside this pilot. No paid add-on is being activated. Production use requires validation of the customer’s workflow, access rules, and platform entitlements.