Document with counterparty verification

ℹ️ The new version of Signi verification will be released to production during September 2026. Until then, the screens in the app may differ slightly from this description.

Most common use: the counterparty of the document must pass identity verification, otherwise they won't reach the signing stage. You set up verification when creating the document for a specific counterparty.

How to do it

1. Create the document as usual and go to the Recipients step.
2. For the counterparty, click the gear icon (recipient settings). The Signi verification section expands with a list of your verification groups.
3. Check the group the counterparty must pass. You can check up to two — the counterparty then chooses which path to verify through.
4. Continue to the document content and send it.

When a group has Automatically add when creating a document enabled, it is pre-filled for the counterparties.

What happens after sending

• The counterparty receives an email; instead of going straight to signing, Signi first guides them through verification.
• In the document detail you can see the verification status for the counterparty (Waiting / Verification in progress / To review / Approved…) and you can Resend the request.
• When the counterparty completes the checks, you review and approve the verification. Only after approval can they sign.

When the counterparty is already verified

Signi recycles valid verifications: if a contact has an approved verification of the same group that is still valid, the counterparty does not go through the checks again — the document goes straight to signing. When verification is requested again is governed by the group's validity and the re-verification threshold in the workspace settings.

If the contact currently has a verification in progress, the app will notify you: „The contact already has a verification in progress. Starting another one will create a new run." Usually it's enough to wait for the existing one to finish.

Where to go next

• Reviewing and approving verification
• Verification from a contact — verification without a document, „in reserve"
• For integrators: Verification with a document via API