DocuSign ID verification options
DocuSign identity verification tiers, when signers must prove identity beyond email links, and planning stronger auth for high-risk envelopes.
Shaan F.
Co-founder & CEO, Atlas
On this page
DocuSign ID verification adds identity proofing before or during signing. Default email-link signing assumes inbox control. Regulated workflows may require government ID, KBA questions, or third-party identity providers.
> Share: "DocuSign ID verification is an add-on lane on top of basic email signing, not the default for every envelope."
Verification methods (typical)
Depending on plan and region:
- ID document upload with liveness check
- Knowledge-based authentication (credit bureau questions)
- SMS or phone verification as secondary factor
- EU eID schemes for qualified workflows
Exact catalog changes by account region. Sandbox test before promising signers a specific UX.
When to enable ID verification
| Scenario | Consider ID verify |
|---|---|
| High-value wire instructions | Yes |
| Internal IT policy ack | Usually no |
| Remote customer onboarding | Often yes |
| Established B2B with known contacts | Case by case |
Friction reduces completion rate. Enable only when risk warrants.
Configuration in DocuSign
Admins attach identity workflows to signing groups or envelope templates. Per-envelope overrides exist for one-off deals.
Reporting shows pass/fail and vendor references for audit.
Cost structure
ID verification often bills per attempt or per successful verification in addition to envelope consumption. Model costs before enabling org-wide.
Atlas perspective
Atlas sign links use tokenized URLs and sequential party promotion. Teams needing step-up identity should map requirements to current Atlas capabilities and legal review before replacing DocuSign ID verify flows.
Consumer disclosure remains on by default for Atlas signers. See /docs/compliance/vendor-security-overview.
Signer support scripts
Help desk should know ID verify failure codes and retry limits. Escalation path when signer lacks required document type prevents deal stall.
Measure completion rate before and after enabling ID verify org-wide. Drop may justify tiered enablement by envelope template not global default.
Operational checklist before you scale
Document the owner for template changes, integration credentials, and signer support escalation. Run a thirty-minute tabletop exercise: candidate cannot open link, finance needs certificate today, API returns 429 during launch. Write answers in internal wiki with envelope ID examples redacted.
Measure time-to-first-completed-envelope for new hires on ops team. If only one person knows admin console, bus factor is high. Export sandbox walkthrough recording when vendor UI updates each quarter.
For hybrid stacks, label outbound emails so signers know which brand hosts their session. Mixed DocuSign and Atlas emails confuse recipients and increase phishing reports to IT.
When migrating vendors, keep legacy read-only login until archive export finishes. Do not cancel production keys until webhook consumers handle new event schema in staging.
Review credit or envelope burn monthly against forecast. Spiky nonprofits and seasonal bulk sends surprise finance if unmonitored.
Train agents and support to request envelope ID first. Guessing from subject line wastes cycles.
Align legal retention on signed PDF plus audit artifacts with IT backup policy. Cloud vendor retention defaults may be shorter than regulatory need.
If signers routinely complete on mobile, test mobile browser on both iOS Safari and Android Chrome before policy mandates ID verification.
Publish internal SLA for signature turnaround separate from vendor uptime SLA. Business expectation management reduces escalations to engineering.
Schedule semiannual access review for admin accounts on signing platform. Former contractors with send permission are a common audit finding.
Document which countries your ID verify vendor supports before launching global hiring. Unsupported ID types block offers at final step.
Pilot ID verify on low-volume template before enabling on standard sales agreement. Measure completion rate drop and help desk ticket volume.
Keep fallback path documented when ID verify vendor outage blocks hiring. Candidates waiting five days cost offers to competitors. HR should know manual workaround before go-live. Include contact in offer letter FAQ. Recruiters should rehearse script once per quarter.
FAQ
Does Atlas accept PDF and DOCX?
Yes. Upload either format when you create an envelope. DOCX files become PDF before anyone signs.
How do I sign in?
Use a Bearer API key from your dashboard settings. MCP connectors in ChatGPT and Claude use OAuth instead.
When do credits get used?
One credit per send, not per upload. You get five free sends when you sign up.
Where should I start?
/docs and API reference.