Send for signature
Add the document and the signer, and send. They receive a secure signing link at their email address — nothing for you to chase.
Send a protected document for signature with a secure link. The recipient opens it from their email and signs — no account, and no re-entering the address you sent it to. When it's signed, it stays protected and tracked, not released as a loose file.
Add the document and the signer, and send. They receive a secure signing link at their email address — nothing for you to chase.
The link identifies the recipient, so there is no account to create and no email to re-enter. They review and sign in the protected viewer.
The signed document keeps its MyPass DRM policy: watermarked to the signer, access you can expire, and a record of who opened it and when.
A generic e-signature tool hands back a loose signed PDF that can be forwarded anywhere. MyPass DRM keeps the signed document inside the same controls as the rest of your protected content — tied to the signer, trackable, and revocable.
Signing becomes part of how you control your content, not a separate step that undoes it.
See all the controlsMember agreements, licensing terms and participation forms — signed, then kept under the same access rules as your standards.
Enrollment agreements, exam integrity policies and instructor contracts — signed by the individual, watermarked to them, expiring when the term ends.
Licensing and distribution agreements — signed and then held under the same controls as the licensed material itself.
Partner, NDA and enablement documents — signed without an account, and revocable when a relationship ends.
No. They open the document from the secure link sent to their email and sign — there is nothing to create.
No. The link already identifies the recipient, so there is nothing to retype. The signature is tied to the address you sent it to.
Yes. It keeps the same MyPass DRM controls as the rest of your content — recipient watermarking, expiry, device limits and access records.
Signing-workflow details and any compliance posture are confirmed for your specific deployment. We do not publish a legal-validity claim here until it is verified for your use case — ask us about your requirements.
Both. Send for signature works on its own, or connected to your platform by API — the same as the rest of MyPass DRM.
The completed document remains in your protected library under its policy. Access, expiry and the activity record continue to apply.
See how sending for signature works — and how the signed document stays protected, watermarked and tracked afterward.