Docusign IAM protects agreements with four layers of security: AES-256 encryption for data at rest, TLS 1.2+ encryption in transit, independent certifications (SOC 1 Type II, SOC 2 Type II, ISO 27001:2022), and account-level access controls enforced through permission profiles. Every completed envelope also gets a Certificate of Completion that records who signed, when, and from where, functioning as a tamper-evident audit trail.

That covers the agreement itself. But most Docusign IAM deployments don't start with a human opening an envelope - they start with a webhook firing from a CRM, an ATS, or a procurement system into Docusign Workflow Builder. That trigger path has its own security model, and it's the part most "Docusign IAM security" roundups skip. This guide covers both: the platform-level security features Docusign documents, and the trigger-layer security questions that come up once you're wiring real integrations.

What security features does Docusign IAM include? #

Docusign IAM is built on the same security program as Docusign eSignature, with four pillars: encryption, independent certifications, identity and access management, and tamper-evident audit records. Docusign's own trust documentation groups these under a single Information Security Program that applies across eSignature, CLM, and IAM products.

How does Docusign IAM encrypt and protect agreement data? #

All agreement data is automatically encrypted with AES 256-bit encryption on upload, and data moving between a user's browser or an API client and Docusign's servers is protected with TLS 1.2 or higher. Docusign's architecture, including its key management setup, is designed so that Docusign personnel cannot read the contents of agreement data in transit or at rest.

For teams evaluating Docusign IAM against internal security requirements, this is usually the first checkbox: data is encrypted both in motion and at rest by default, with no separate configuration needed to turn it on.

What certifications back Docusign IAM's security claims? #

Docusign's Information Security Program is independently audited and certified under ISO 27001:2022, ISO 27017:2015, and ISO 27018:2019, covering information security management, cloud security, and cloud privacy respectively. Docusign also completes annual SOC 1 Type II and SOC 2 Type II audits under AICPA Trust Services Criteria, which assess security, availability, processing integrity, and confidentiality controls over a 6 to 12 month observation period rather than a single point-in-time check.

How does Docusign IAM control who can access agreements? #

Docusign IAM uses permission profiles: reusable sets of account-level and Agreement Manager permissions that administrators assign to users or groups. A profile can combine broad account permissions (who can manage users, who can send on behalf of others) with narrower Agreement Manager permissions that control which agreement sets a given user can see or edit. Set-level roles (Set Viewer, Set Collaborator, Set Manager) layer on top of agreement-level access, so a user's actual reach on any given contract is the intersection of their profile and the specific set and agreement permissions assigned to them.

This matters for anyone automating Docusign from the outside. If a webhook-triggered workflow creates an envelope on behalf of a sales rep, that rep's permission profile, not the integration, still governs what they can see and do with the resulting agreement.

Does Docusign IAM support single sign-on and domain-level access control? #

Yes. Docusign Admin's Access Management with SSO add-on lets an organization claim its email domain, connect a SAML identity provider, and require every user under that domain to authenticate through the company's own SSO rather than a separate Docusign password. Once a domain is claimed, Docusign can automatically provision new users the first time they log in through the identity provider (just-in-time provisioning), so access follows a company's existing joiner-mover-leaver process instead of a parallel list of Docusign accounts an admin has to manage by hand.

This closes a real gap: without a claimed domain, every sender can have an independent password, and a departing employee keeps access to Docusign until someone manually closes the account. With SSO enforced, deprovisioning a user in the identity provider is enough to cut off Docusign access too.

How does Docusign IAM prove an agreement wasn't tampered with? #

Every completed envelope gets a Certificate of Completion, which records envelope details, recipient events (who viewed, who signed, when), and summary events with timestamps. This certificate is the document most legal and compliance teams point to when an agreement's validity is questioned, and it's what distinguishes a Docusign-executed contract from a plain PDF with a pasted signature image.

For audit-heavy workflows (finance, procurement, HR), the Certificate of Completion is the artifact to pull into your own record-keeping system, not just the signed PDF. If you're automating contract creation through Workflow Builder, make sure whatever stores the final agreement also retains the certificate, not just the document.

Where does webhook security fit into the Docusign IAM picture? #

Everything above protects the agreement itself. But a growing share of Docusign IAM usage starts earlier in the chain: a CRM stage change, a new hire in an ATS, or a new PO in a procurement system fires a webhook that triggers a Docusign Workflow Builder workflow before any envelope exists. That trigger path has a security model of its own, and it's where Docusign Connect and webhook relays like Baton come in.

Docusign Connect, the webhook layer, signs each outbound delivery with an HMAC-SHA256 digest over the raw request body, sent in the X-Docusign-Signature-1 header (with -2, -3, and so on for each additional active key, up to 100). A receiving system is supposed to recompute that HMAC with its own copy of the shared key and reject anything that doesn't match. One detail worth flagging: Connect deliveries are unsigned by default - HMAC has to be explicitly enabled on the Connect configuration, and the key is only shown once at creation time.

This is the piece that matters if you're building or evaluating the plumbing between a source system and Docusign Workflow Builder. Baton sits in exactly that position: a source platform fires a webhook, Baton verifies the HMAC signature on the delivery, matches the payload fields to a Workflow Builder workflow's parameters, and triggers the run. Baton never stores API keys or credentials for the source platform itself; it holds only the Docusign-side credentials needed to call Workflow Builder, and it accepts inbound events strictly through webhook URLs, not an OAuth connection into HubSpot, Salesforce, or whatever system is upstream. That's a deliberate scope boundary: fewer stored credentials on the source side means a smaller blast radius if any single integration is compromised.

It's worth being precise about what this trigger layer does and doesn't do. A relay like Baton triggers a Workflow Builder workflow; it's that workflow, not the relay, that creates the resulting envelope. If you're troubleshooting a missing agreement, the failure domain is different depending on whether the trigger never fired (a Baton/Connect problem) or the workflow fired but stalled downstream (a Workflow Builder problem). Our deep-dive on why Docusign webhooks fail silently walks through how to tell the difference.

Docusign IAM security features at a glance #

LayerFeatureDetail
Data protectionEncryption at restAES-256 on upload
Data protectionEncryption in transitTLS 1.2+
CertificationInformation securityISO 27001:2022
CertificationOperational controlsSOC 1 Type II, SOC 2 Type II
Access controlPermission profilesAccount + Agreement Manager permissions, assignable to users/groups
Access controlSet-level rolesSet Viewer, Set Collaborator, Set Manager
AuditCertificate of CompletionPer-envelope record of signer events and timestamps
Trigger securityConnect HMAC signatureHMAC-SHA256 over raw body, X-Docusign-Signature-N header

What to check before you trust a Docusign IAM deployment #

If you're responsible for securing a Docusign IAM rollout, verify these in order: confirm encryption settings aren't something you need to configure (they're on by default), request the current SOC 2 report from Docusign's Trust Portal if your compliance team needs it on file, audit your permission profiles so senders and viewers hold the least privilege that still lets them work, confirm Certificate of Completion attachment is enabled wherever contracts get archived, and if you're triggering workflows from an external system, confirm HMAC is turned on in your Connect configuration and that whatever receives those webhooks actually checks the signature instead of trusting the payload. For a broader map of how IAM's pieces fit together beyond security, see what's actually inside Docusign IAM, app by app.

If you're building the trigger side of that last point and want to skip writing your own HMAC verification and retry logic, see how Baton wires this up or start with a workflow you already have running in Workflow Builder.