What Approvers See: The Approval Experience

If you're about to make someone an approver, or you've just become one, here's exactly what that role looks like from the inside. 

The Approver's Flow 

1.  An email arrives, styled like a signing invitation but asking for review. 

2.  The document opens in a read-focused view: no fields to fill; approvers evaluate, they don't sign. 

3.  Two buttons: Approve or Reject, each with an optional note (for rejections, the note is effectively required, since the sender needs to know why). 

4.  Done. The approver's part is over in minutes. 

What Happens With Their Decision 

•  Approve → signing invitations go out automatically; the approver can track the request to completion if they wish. 

•  Reject → the request stops before any signer is contacted; the sender gets the reason and fixes accordingly. 

•  Either way, the decision is timestamped in the audit trail with the approver's identity: governance with receipts. 

Note: Identity verification (Email OTP) applies to approvers too, if the sender set it on their row.