AtlasWork, planned itself.

    The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

    System status
    • SSO
    • SCIM
    • Two-factor sign-in
    • Audit log

    Product

    • Overview
    • PDF tools
    • Diagram tools
    • People & HR
    • Integrations
    • Marketplace
    • Pricing

    Resources

    • Guides
    • Glossary
    • Compare
    • Docs
    • API reference
    • Support
    • Changelog
    • Status

    Company

    • About
    • Careers
    • Press
    • Contact

    Legal & trust

    • Trust center
    • Security
    • Privacy
    • Terms
    • DPA
    • GDPR
    • SLA
    • Refunds
    • Google API data
    Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
    PrivacyTermsSecurityStatus

    You are in control of your cookies

    Atlas uses strictly necessary cookies to keep you signed in. With your consent, we add anonymized product analytics, conversion attribution, and remembered preferences. Change your mind any time at /privacy/cookies.

    Off until you agree · Change it any time

    • NecessaryAlways on
    • AnalyticsOpt-in
    • MarketingOpt-in
    • PreferencesOpt-in
    Still loading. Try again in a moment.Still loading. Try again in a moment.Still loading. Try again in a moment.
    Skip to documentation
    Docs
    Back to Atlas

    Start here

    • Overview

    Developer

    • REST API guide
    • Authentication
    • API reference
    • MCP (AI agents)
    • MCP tools reference
    • SDKs
    • Quick actions
    • Changelog

    Webhooks

    • Overview
    • Quickstart
    • Events
    • Payloads and headers
    • Security and signing
    • Delivery and retries
    • Managing via API

    Connect

    • Connectors
    • Integrations

    Product

    • Collaboration and chat
    • Signing in and security
    • Client portal
    • Client portal domains

    Reference

    • Glossary
    • Keyboard shortcuts
    • Module reference
    Module reference

    Module guide

    Document Sign

    Envelope preparation, signer routing, reminders, certificates, and audit trails.

    Open module/document-sign
    documentslegal

    Overview

    Document Sign is the e-signature workspace for envelope preparation, signer routing, signing links, reminders, approvals, templates, completion certificates and audit evidence. It starts from its own templates and envelopes, and it can also take a contract from Contract Hub.


    Highlights

    The capabilities worth knowing before you dive in.

    • Overview of the envelope funnel from drafted, sent and viewed through in progress to completed, with counts of declined, expired and voided envelopes
    • Searchable action finder for envelopes, recipients, reminders, audit trails and completed documents
    • Template builder with sequential, parallel or conditional signer routing, signer sessions and completion certificates
    • Reminder, legal-review, lifecycle sweep, and audit package actions
    • Bulk send of one template to many recipients from a CSV file
    • A hash-chained audit trail for every envelope, with a completion certificate and a downloadable audit package
    • Median time to sign and a count of stuck envelopes that are eligible for a reminder
    • Three emails keep an envelope moving: an invitation with a personal signing link for each signer, a reminder when the sender asks for one or when the reminder interval of the envelope falls due, and a completion email to the sender when the last signer has signed
    • Sequential order invites the first signer and then each next signer once the one before has signed, and parallel order invites every signer at once
    • A signed document that is the original PDF with every signature, initials, date, text and checkbox placed on its field, followed by a signature summary page, and a separate completion certificate
    • Names, titles and field text print correctly on the signed document and the certificate in Latin, Greek, Cyrillic, Japanese, Chinese, Arabic, Hebrew and Hindi
    • Templates that keep the document, the signer roles and the field layout, saved from the review step of a new agreement or created directly, and then used, renamed or archived from the Templates page. Bulk send needs no second upload for a template that stores its own document

    Important to know

    Limits, permissions, and sharp edges to keep in mind.

    • Signing is native to Atlas: envelopes, signing links, completion certificates and audit trails are produced by Atlas itself, not by an outside signature service.
    • Signing links and tokens are credentials, so they are kept out of analytics and out of the documentation.
    • An envelope can end as completed, declined, expired or voided, and the Overview counts each outcome.
    • The source PDF can be at most 25 MB, an envelope can have at most 50 signers and 100 fields, and a PDF that is encrypted, damaged or empty is refused with a message that says what to change.
    • A signer must give a reason to decline. A decline ends the whole envelope as declined, nobody can sign it afterwards, and the reason is recorded in the audit trail.
    • An envelope can carry an expiry date. Atlas checks every hour and marks an envelope as expired once that date has passed. Each signing link is also valid for 30 days.
    • A field on a page that is rotated is placed where the signer saw it, because its position is measured on the page as it is displayed.
    • The signed document and the completion certificate are available to the sender, to the signers, and to workspace owners and administrators once every signer has signed.
    • A template keeps roles, not people. Signer names and email addresses are never saved in a template. The name of a template can have at most 200 characters and its description at most 5000. Archiving a template removes it from the Templates page and from bulk send, and does not change agreements already made from it. A template saved before documents were stored asks for the PDF again when it is used.

    How to use it

    The primary workflow, start to finish.

    1. 1Open /document-sign and, on the Envelopes page, search the action finder for the job you need.
    2. 2Use the Overview page for the envelope funnel, the outcomes, the median time to sign and the envelopes that are stuck.
    3. 3Prepare an envelope from a template or source PDF.
    4. 4Choose sequential, parallel or conditional routing for the signers.
    5. 5Send the envelope, send reminders and track lifecycle events.
    6. 6Download certificates, audit packages, and signed-PDF evidence when complete.
    7. 7If a signer declines, read the reason in the audit trail, change what the signer objected to and send a new envelope.
    8. 8When every signer has signed, download the signed document and the completion certificate from the envelope. The sender receives a completion email with a link to it.
    9. 9To make a template, choose Save as template on the review step of a new agreement, or Create a template on the Templates page. To use one, choose Use template on its card: the document, the signer roles and the fields arrive filled in, and you add only the people who sign.

    FAQ

    Can I use Document Sign without PDF Studio?
    Yes. Document Sign is its own module and does not need PDF Studio.
    Do I need an outside signature service?
    No. Document Sign produces the signing links, completion certificates and audit trails itself.
    Are signing links shown in analytics or in the documentation?
    No. A signing link is a credential, so links and tokens are kept out of analytics and out of the documentation.
    What happens when a signer declines?
    The envelope ends as declined and no other signer can sign it. The signer must give a reason, and the reason is recorded in the audit trail. To try again, send a new envelope.
    How long does a signer have to sign?
    Each signing link is valid for 30 days. You can also set an expiry date on the envelope, and Atlas marks the envelope as expired once that date has passed. Send a new envelope when a link has expired.
    How large can the document be?
    The source PDF can be at most 25 MB. If the file is larger, compress it or split it into parts. An envelope can have at most 50 signers and 100 fields.
    Do names in Japanese, Chinese, Arabic, Hebrew or Hindi print correctly on the signed document?
    Yes. The signed document and the certificate embed fonts for these scripts, so a name prints as it was entered. Chinese is covered in its simplified characters, and a character that no embedded font holds is shown as an empty square, never as a question mark.

    Automate this module

    Everything on this screen is scriptable. Drive it from the REST API, or let an AI agent run it through the MCP server.
    All modules
    Was this page helpful?
    About this page

    On this page

    • Overview
    • Highlights
    • Important to know
    • How to use it
    • FAQ