Document Sign

Document Sign is the standalone e-signature workspace for envelope preparation, routing, signing sessions, reminders, approvals, templates, certificates, signed-PDF handoff, and audit evidence. It can receive PDFs from PDF Studio or contracts from Contract Hub, but it can also start from its own templates and envelopes.

• Envelope lifecycle dashboard with draft, sent, signed, expired, voided, and completed states
• Searchable Document Sign Action Catalog for envelopes, recipients, sessions, templates, fields, lifecycle, evidence, and optional handoffs
• Template builder, field routing, conditional rules, signer sessions, and certificate generation
• Reminder, legal-review, lifecycle sweep, and audit package actions
• Each cataloged signing action names its user control, validation rule, app API route or standalone module boundary, and MCP target
• Optional signed-PDF handoff back into PDF Studio for artifact verification and export
• Provider-neutral design ready for DocuSign, Dropbox Sign, PandaDoc, or Adobe-backed adapters

• Atlas-owned signing records work without live provider keys; provider delivery is activated when credentials and scopes are configured.
• Signing links, tokens, and raw provider payloads are not exposed in analytics or docs.
• PDF Studio integration is a handoff, not a dependency.

1. 1Open /document-sign and search the Document Sign Action Catalog for the job you need.
2. 2Use the signing command center when you want envelope posture, pending signatures, and governance state.
3. 3Prepare an envelope from a template or source PDF.
4. 4Route signers sequentially or in parallel depending on policy.
5. 5Issue signing sessions, send reminders, and track lifecycle events.
6. 6Download certificates, audit packages, and signed-PDF evidence when complete.

Can I use Document Sign without PDF Studio?

Yes. PDF Studio is helpful for source preparation and artifact review, but signing envelopes remain their own module.

What happens if provider keys are not configured?

Provider-backed actions stay unavailable or disabled while Atlas-owned records, templates, and readiness evidence remain visible.

Where can I see the signing link or the provider payload?

Nowhere in analytics or in the documentation, by design. Signing links, tokens and raw provider payloads are deliberately not surfaced, because a signing link is a credential.