Signing Experiences
Signing experiences are reusable configuration profiles for how recipients receive, view, and complete documents.
They let you control behavior at the recipient level without redesigning the document itself.
What a signing experience controls
A signing experience can affect:
- email branding
- recipient language
- signing page behavior
- agreement statements
- download and delivery behavior
- some security and verification options
This means the same template can be used in different ways for different recipients or teams.
Why experiences matter
Experiences separate document structure from recipient behavior.
That makes them useful when:
- different recipients need different languages
- branding varies across teams or workflows
- one workflow needs stricter controls than another
- you want to reuse the same template across different business cases
Team-level and recipient-level use
Experiences can be used as defaults, but they are also useful at a more granular level. In practice, they become one of the main ways to adapt a workflow without rebuilding the template.
Common experience-driven changes
Typical changes made through experiences include:
- custom email branding
- custom subject lines and email text
- agreement statements
- recipient language
- witness and security settings
Experiences and workflow design
Experiences work best when they are treated as reusable workflow building blocks rather than one-off edits.
For example, instead of changing the same settings repeatedly, create named experiences for:
- standard internal signing
- customer-facing branded signing
- witness-required signing
- language-specific signing