Permissions
Permissions
Expanded by eSignature REST API 2.1Users defined in Docusign accounts each have a permission profile that determines which actions they are allowed to perform.
- Each user must have a permission profile
- You can define any number of permission profiles
- Each permission profile may be assigned to any number of users
By defining permission profiles for common types of users, you can simplify managing large numbers of users in an account. Whenever you need to update the permissions for a group of users, you can update their permission profile in a single operation rather than updating each user on an account-by-account basis.
Three default permission profiles are preset for all Docusign accounts:
- DS Admins have all DS Sender permissions and can additionally send envelopes to bulk lists, share templates, view and manage envelope rights through the API, send on behalf of other users through the API, and create web forms.
- DS Senders can view and send envelopes, create and use templates, use signer attachments, and use supplemental documents.
- DS Viewers can view envelopes.
You can download a CSV file showing the details of each permission for each permission profile in your account through your eSignature Admin Permission profiles page. See Download Permission Profiles Data for details.
These permission profiles cannot be modified or deleted, but you can view them, copy them, and use them as the basis for creating new permission profiles. See Add and Copy Permission Profiles for details.
In version 2.1 of the eSignature API, you can add, update, and remove permission profiles from your account via the API AccountPermissionProfiles resource, in addition to via the UI. See the Permission Profiles eSignature Admin Guide for details on working with permission profiles using the UI.
Note: See the settings definition in the AccountPermissionProfiles API reference to learn about the full set of permission profile options and about what each option controls.
Not all permissions are available for all accounts; your account plan must have access to a feature before you can enable permissions to use it.
Next steps
Working with permission profiles? See code examples on: