Stitchflow
Docusign logo

Docusign User Management Guide

Manual workflow

How to add, remove, and manage users with operational caveats that matter in production.

UpdatedMar 5, 2026

Summary and recommendation

Docusign user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.

Docusign user management runs through Settings → Users & Groups → Users in the admin console. Every app in your stack that handles contracts or signatures ties back to who holds an active Docusign seat, making accurate provisioning directly relevant to both access control and billing.

SCIM and SAML SSO are gated behind the Enterprise plan, which carries custom pricing; all lower tiers require fully manual user lifecycle management.

Quick facts

Admin console pathSettings → Users & Groups → Users
Admin console URLOfficial docs
SCIM availableYes
SCIM tier requiredEnterprise
SSO prerequisiteYes

User types and roles

Role Permissions Cannot do Plan required Seat cost Watch out for
Account Administrator Full account management: add/remove/deactivate users, manage permission profiles, configure SSO/SAML, manage billing, access all envelopes in the account, configure account-level settings. Cannot exceed envelope or user seat limits set by the purchased plan without upgrading. Cannot delete envelopes permanently in most configurations. Standard and above (at least one admin seat required on all paid plans) Consumes a paid user seat Admin role is assigned via a permission profile, not a separate seat type. Any user can be made an admin by assigning the 'DS Admin' permission profile.
Sender (Standard User) Send envelopes, use templates, manage own envelopes, access DocuSign Rooms if licensed. Permissions vary based on assigned permission profile. Cannot manage other users, configure account settings, or access other users' envelopes unless granted shared access. All paid plans (Personal, Standard, Business Pro, Enterprise) Consumes a paid user seat Personal plan is single-user only; multi-user accounts require Standard or above.
DocuSign Viewer / Recipient Can sign and view documents sent to them. No account login required for basic signing. Cannot send envelopes, access the admin console, or manage documents unless they hold a paid seat. No seat required to receive/sign; seat required to send. No seat cost for recipients who only sign Recipients do not need a Docusign account to sign; they receive an email link. Only senders consume seats.
DocuSign CLM User Access to Contract Lifecycle Management module: create, negotiate, and manage contracts. CLM access is separate from eSignature; a user with an eSignature seat does not automatically have CLM access. Enterprise (CLM is an add-on product) Separate CLM seat cost; pricing is custom/negotiated CLM admin configuration is separate from eSignature admin. SSO and permission profiles must be configured independently for each product.

Permission model

  • Model type: permission-sets
  • Description: Docusign uses Permission Profiles - named sets of granular permissions assigned to users. Built-in profiles include 'DS Admin', 'DS Sender', and 'DS Viewer'. Admins can create custom permission profiles on Business Pro and Enterprise plans. Profiles control capabilities such as sending envelopes, managing templates, using bulk send, accessing reporting, and sharing envelopes.
  • Custom roles: Yes
  • Custom roles plan: Business Pro and Enterprise
  • Granularity: Granular: individual toggles for sending, template management, bulk send, shared access, reporting, API access, and more within each permission profile.

How to add users

  1. Log in to Docusign as an Account Administrator.
  2. Navigate to Settings (gear icon, top right) → Users & Groups → Users.
  3. Click 'Add User'.
  4. Enter the user's first name, last name, and email address.
  5. Select a Permission Profile (e.g., DS Sender, DS Admin, or a custom profile).
  6. Optionally assign the user to one or more Groups.
  7. Click 'Add User' to send an activation email to the new user.
  8. The user must click the activation link in the email to set their password and activate their account.

Required fields: First name, Last name, Email address, Permission Profile

Watch out for:

  • Adding a user immediately consumes a paid seat and may trigger a prorated billing charge if at the seat limit.
  • The activation email expires; if the user does not activate within the expiry window, the admin must resend the invitation.
  • Email address must be unique across all Docusign accounts; if the email is already associated with another Docusign account, the user will be prompted to merge or use a different address.
  • On the Personal plan, only one user (the account owner) is supported; additional users require upgrading to Standard or above.
  • Users added via the admin console are not automatically provisioned into CLM or other Docusign products - each product requires separate user setup.
Bulk option Availability Notes
CSV import Yes Settings → Users & Groups → Users → Add User → Import Users (CSV upload option)
Domain whitelisting No Automatic domain-based user add
IdP provisioning Yes Enterprise (requires SAML SSO setup plus SCIM 2.0 configuration; one-time SAML activation fee applies)

How to remove or deactivate users

  • Can delete users: No
  • Delete/deactivate behavior: Docusign does not allow permanent deletion of user accounts from the admin console. Users can only be 'closed' (deactivated). A closed user cannot log in or send envelopes, but their account record and all associated envelope history are retained. The user's email address remains tied to the account and cannot be reused for a new user on the same account.
  1. Log in to Docusign as an Account Administrator.
  2. Navigate to Settings → Users & Groups → Users.
  3. Locate the user using search or the user list.
  4. Click the user's name to open their profile.
  5. Click 'Close User' (or select 'Close' from the Actions menu).
  6. Confirm the action in the dialog. The user's status changes to 'Closed' immediately.
Data impact Behavior
Owned records All envelopes sent by the closed user remain in the account and are accessible to administrators. Envelope history and audit trails are preserved.
Shared content Templates created by the closed user remain in the account and can be reassigned or accessed by admins. Shared folders and documents remain accessible to users who had shared access.
Integrations Any API integrations or connected apps using the closed user's credentials or OAuth tokens will stop functioning. Admins should rotate credentials before closing the user.
License freed Closing a user frees the seat, making it available to assign to a new user without additional cost (within the purchased seat count).

Watch out for:

  • A closed user's email address cannot be reused for a new user on the same Docusign account, which can cause issues when employees are rehired or change email addresses.
  • Closing a user does not automatically reassign their in-progress envelopes; any envelopes awaiting action may stall and require manual intervention by an admin.
  • Admins cannot bulk-close users from the UI; each user must be closed individually through the admin console.
  • If the closed user was the sole admin on the account, another user must be promoted to admin before closing them.
  • SCIM-provisioned users closed via the IdP are deactivated in Docusign, but the same email-reuse restriction applies.

License and seat management

Seat type Includes Cost
Personal 1 user seat, 5 envelopes/month, basic sending and signing $10/month (annual) or $15/month (monthly)
Standard Multi-user support, unlimited envelopes, basic admin console, standard permission profiles $25–$45/user/month depending on billing cycle and seat count
Business Pro All Standard features plus advanced fields, bulk send, custom permission profiles, signer attachments, payment collection $40–$65/user/month depending on billing cycle and seat count
Enterprise All Business Pro features plus SAML SSO, SCIM provisioning, advanced reporting, API access, CLM add-on eligibility, dedicated support Custom pricing (negotiated per contract)
  • Where to check usage: Settings → Billing & Usage → Plan & Billing (shows current seat count, seats used, and envelope consumption)
  • How to identify unused seats: Navigate to Settings → Users & Groups → Users and filter by 'Last Login' date or sort by activity. Users who have never logged in or have not logged in recently can be identified for deactivation. There is no built-in automated 'inactive user' report; admins must manually review the user list.
  • Billing notes: Seats are billed per user per month. Adding users mid-cycle results in prorated charges. Closing (deactivating) a user frees the seat for reassignment but does not automatically reduce the contracted seat count - seat count reductions require contacting Docusign sales or waiting for contract renewal. Annual plans carry a 30-day refund guarantee. SAML SSO on Enterprise requires a one-time activation fee in addition to per-seat costs.

The cost of manual management

Adding a user immediately consumes a paid seat and may trigger a prorated charge if you are at your seat limit. Closing a user frees the seat for reassignment but does not reduce your contracted seat count - that requires contacting Docusign sales or waiting for renewal.

There is no bulk-close option in the admin UI, so every offboarding is a one-at-a-time operation. Identifying unused seats also requires manual review: Docusign has no built-in inactive-user report, so admins must sort the user list by last-login date themselves.

What IT admins are saying

The friction points that surface most consistently from Docusign admins center on three areas. First, closed user email addresses cannot be reused on the same account - a hard constraint that causes real problems when employees are rehired or email addresses need correction.

Second, CLM and eSignature user management are entirely siloed; a change in one product does not propagate to the other, requiring duplicate admin work.

Third, the one-time SAML SSO activation fee on Enterprise is frequently flagged as an unexpected cost not prominently disclosed during the sales process.

Common complaints:

  • One-time activation fee for SAML SSO on top of enterprise pricing is unexpected and not prominently disclosed during sales.
  • Closed user email addresses cannot be reused on the same account, causing friction when rehiring employees or correcting email address mistakes.
  • No bulk-close option in the admin UI; admins must deactivate users one at a time.
  • No built-in inactive user report; identifying unused seats requires manual review of last-login dates.
  • CLM and eSignature user management are siloed - changes in one product do not propagate to the other.
  • Limited permission profile granularity with some IdP integrations; not all permission profile assignments sync correctly via SCIM.
  • Activation emails for new users can expire without clear notification to the admin, leaving users unable to log in.
  • Seat count reductions require contacting sales and cannot be self-served through the admin console.

The decision

Manual management is viable for teams with stable headcount and infrequent onboarding cycles, particularly on Standard or Business Pro plans where SCIM is not available. Once your organization is adding or removing users regularly, the absence of bulk actions and inactive-user reporting turns routine hygiene into a recurring time sink.

Every app that touches identity at scale eventually hits the same ceiling: per-user manual steps do not compress. If your team is on Enterprise and has an IdP already configured for SAML, enabling SCIM is the operationally sound path forward.

Bottom line

Docusign's admin console gives Account Administrators direct control over user provisioning, permission profiles, and seat assignment, but the manual workflow has hard limits: no bulk deactivation, no automated inactive-user detection, and a closed-user email reuse restriction that creates friction at offboarding.

Seat costs accrue immediately on user creation and do not self-correct when users are closed, so license hygiene requires active attention.

For organizations on Enterprise with SSO already in place, SCIM provisioning removes the per-user manual overhead and is the recommended approach for any team managing more than a handful of seats.

Automate Docusign workflows without one-off scripts

Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.

Every app coverage, including apps without APIs
60+ app integrations plus browser automation for apps without APIs
IT graph reconciliation across apps and your IdP
Less than a week to launch, maintained as APIs and admin consoles change
SOC 2 Type II. ~2 hours of your team's time

UpdatedMar 5, 2026

* Details sourced from official product documentation and admin references.

Keep exploring

Related apps

15Five logo

15Five

Full API + SCIM
AutomationAPI + SCIM
Last updatedFeb 2026

15Five uses a fixed role-based permission model with six predefined roles: Account Admin, HR Admin, Billing Admin, Group Admin, Manager, and Employee. No custom roles can be constructed. User management lives at Settings gear → People → Manage people p

1Password logo

1Password

Full API + SCIM
AutomationAPI + SCIM
Last updatedFeb 2026

1Password's admin console at my.1password.com covers the full user lifecycle — invitations, group assignments, vault access, suspension, and deletion — without any third-party tooling. Like every app that mixes role-based and resource-level permissions

8x8 logo

8x8

Full API + SCIM
AutomationAPI + SCIM
Last updatedFeb 2026

8x8 Admin Console supports full lifecycle user management — create, deactivate, and delete — across its X Series unified communications platform. Every app a user can access (8x8 Work desktop, mobile, web, Agent Workspace) is gated by license assignmen