Approvals System
Sequential or parallel approval workflows with token links, required denial reasons, and a full audit trail.
The approvals system routes documents through sequential or parallel approval chains, with field assignment per approver and a complete history of every approval action.
How it works
You configure an approval chain that matches your sign-off pattern, then approvers receive token links that open directly to their approval action. Approvers approve with a single click or deny with a required reason, and every action is logged to the contract's audit trail with IP address and geolocation.
Approvers differ from signers. An approver reviews and signs off on a document for the next step but never adds a signature to it. Approval workflows are one of the seven workflow types supported by signing workflows, and approvers can be configured through recipient management as the approver role.
Key capabilities
- Sequential routing where each approver completes before the next is notified, or parallel routing where all approvers can act at once. The pattern is picked per workflow.
- Field assignment per approver, so each approver sees only the fields their role requires.
- Time limited token links that open directly to the approval action with no login required. Tokens expire after a configurable window, typically 7 to 30 days.
- Required reason on denial, captured as part of the audit trail. Approval takes a single click.
- Full approval history showing who approved, when, from where, and any denial reason, filterable by approver, date range, or status.
- IP address and geolocation captured on every approval and denial action.
Tips
Use sequential routing when each approver's review depends on the previous one, and parallel routing when approvers can review independently and speed matters. Many teams combine both at different stages of a single workflow.