Signer Verification
No. A Peekop link alone is not signing authority.
Only the designated signer who completes exact recipient email verification receives Verified Access and can enter the protected signing session.
Product Evidence

Common Assumption
Many people assume that if someone forwards a signing link, the new person can sign. That is not how Peekop's protected signing flow works.
A signing link provides access to the signing request. It does not automatically grant authority to perform protected signing actions.
In Peekop's model, a Recipient-Specific Link is the beginning of the flow, not the end of the trust decision.
Those actions are protected behind Verified Access and a Protected Signing Session.
What Happens Next
A Peekop signing request starts with a recipient-specific link created for the intended signer.
Before protected document actions can continue, the recipient confirms the exact email associated with that request.
After verification succeeds, access is treated as trusted recipient access for that request.
Signing actions occur inside a protected signing session rather than through unrestricted public-link access.
After Verified Access is established and the protected signing session begins, Peekop can preserve signing actions, Signing Started, and the Completion Record.
Forwarding a link does not automatically grant signing authority.
A forwarded user would still need to satisfy recipient verification requirements before protected signing actions can occur.
That is the core difference between link possession and signing authority.
| Concept | What it means |
|---|---|
| Link Possession | Can reach the signing request. |
| Signing Authority | Requires recipient verification and protected session access before protected signing actions can occur. |
After Verified Access is established, Peekop can preserve evidence that supports what happened throughout the signing journey.
Audit metadata supports the evidence trail after verification. It is not the primary explanation of signing authority on its own.
No. A Peekop link alone is not signing authority. Only the designated signer who completes exact recipient email verification receives Verified Access and can enter the protected signing session.
Forwarding a link does not automatically grant signing authority. A forwarded user would still need to complete exact recipient email verification before protected signing actions can occur.
Yes. Peekop requires exact recipient email verification before Verified Access is granted and protected signing actions are allowed.
No. Peekop uses recipient-specific signing links and Verified Access rather than unrestricted link-based access.
Peekop removes the friction of forced recipient account creation, but it still uses recipient verification before protected signing actions begin.
Verified Access is the trusted access state reached after the intended recipient completes the required verification step for that signing request.
A protected signing session is the signing environment entered after Verified Access is established and before protected signing actions occur.
Peekop can preserve Verified Access, Signing Started, completion timing, completion evidence, and the Completion Record after signing is complete.