How to require learners to sign content for completion — for policies, agreements, and compliance content where attestation matters.
E-Signatures turn passive content consumption into active attestation. With E-Signatures enabled on an Article or File, learners can't mark it complete just by viewing — they have to type their name and explicitly check a confirmation box.
Reach for E-Signatures when compliance, legal, or HR programs require evidence that the learner explicitly acknowledged the content. The signature field appears in reports with a timestamp, providing the audit trail.
For the strategic frame on compliance programs, see Compliance Programs in Continu.
How to Enable E-Signatures
1. Open the content's edit settings. In the Settings step during Article or File creation/editing, toggle on Require E-Signature.
2. Customize the agreement text (optional). Click Edit Agreement Text under the toggle to change the wording learners will sign. Default text works for most cases; customize when compliance or legal teams require specific language.
3. Save and publish. Finalize other edits and click Publish Changes.
What Learners See
When a learner opens E-Signature-enabled content, they're prompted to type their name and check the confirmation box. The content remains incomplete until both are submitted.
After signing, the content marks complete. Learners who don't sign keep receiving "signature required for completion" notifications.
The signature event flows into reports with a timestamp — surface this in compliance reporting to show what was signed, when, and by whom.
What Makes Good E-Signature Usage
Reserve for content where attestation matters. E-Signatures add friction. Use them when the friction is the point — policy acknowledgment, code of conduct, signed agreements. Avoid them on general learning where forced signing feels heavy-handed.
Customize the agreement text for legal precision. Default agreement text works for most cases, but legal/compliance content often requires specific language. Coordinate the wording with the team that owns the policy before publishing.
Pair with notifications. Learners who skip the signature get reminders. Make sure the reminder cadence matches the program's compliance timeline — too few and people forget; too many and they tune out.
Configuration Pitfalls
E-Signature Without Compliance Reason. If the content doesn't need attestation, E-Signatures add friction that hurts completion. Only enable when the signature serves a purpose.
Default Agreement Text on Legally-Significant Content. Generic agreement language won't hold up if a legal team needs specific wording. Customize before publishing on anything compliance-sensitive.
Forgetting to Set Up Notifications. A learner who doesn't sign and doesn't receive reminders may stay unsigned indefinitely. Verify reminder Automations are configured for E-Signature content.
Enabling on Read-Heavy Content Without Considering Mobile. Long policies on mobile + a signature prompt at the end = high drop-off. Either break the content into shorter segments each with its own signature, or note that mobile completion is suboptimal for this content.
Where This Fits
You're here because you need attestation on content completion. The strategic compliance frame lives in Compliance Programs in Continu. For other content settings, see Editing Content Settings.
See Also
- Compliance Programs in Continu — the strategic anchor.
- Add an Article to Continu — Article creation flow.
- Add Files Content (PowerPoint, PDF, etc.) — File creation flow.
- Enable Content Certificates — pair E-Signatures with certificates for full attestation evidence.
Enable for compliance and policy content. Customize the agreement text when legal precision matters. Surface signed-at timestamps in compliance reporting.