How to delete user product permission profiles using an email address
This topic demonstrates how to list and delete Docusign Admin user product permission profiles.
- This endpoint can only be used by organizations that have purchased Docusign plans for both CLM and eSignature.
- If the eSignature permission profile of the last eSignature admin user is deleted, admin access will be removed from that account. Similarly, if the CLM permission profile of the last CLM admin user is deleted, CLM access will be removed from the account.
- If the eSignature permission profile of a user is deleted, the user will be deleted from the account.
- The user’s eSignature permission profile cannot be deleted if the user has a CLM permission profile. First delete the user’s CLM permission profile, then delete the user’s eSignature permission profile.
Run this code example from our Quickstart or launcher projects: Bash, C#, Java, Node.js, PHP, PowerShell, Python, or Ruby.
Required data
Running the code in this how-to requires this data:
Step 1. Obtain your OAuth token
To make the API calls shown in this how-to, you need a valid OAuth access token. Docusign supports access tokens for three different recommended OAuth grant types: Public Authorization Code Grant, Confidential Authorization Code Grant, and JSON Web Token (JWT) Grant. Choose the OAuth grant type appropriate for your scenario.
Docusign Admin OAuth access tokens are the same ones used for our eSignature REST API, although you must request one or more Docusign Admin scopes to call the Docusign Admin API. The endpoint calls made in this how-to require that you request the Docusign Admin-specific user_write scope when obtaining your access token.
See Docusign Admin Authentication for details and the full list of Docusign Admin scopes.
Step 2. Construct your API headers
After you have a valid OAuth access token, you are ready to construct the API headers that you will pass to the API call. Construct your headers like this, but make sure to substitute your valid OAuth access token for {ACCESS_TOKEN}.
Step 3. Retrieve user product permission profiles
Make a GET request to the MultiProductUserManagement:getUserProductPermissionProfilesByEmail endpoint to retrieve the product permission profiles associated with a user email address.
Here’s how you make the call, but make sure to substitute your organization ID for {ORGANIZATION_ID}, your API account ID for {API_ACCOUNT_ID}, and the desired email address for {EMAIL_ADDRESS}.
Step 4. Create the request body
To delete a user product permission profile, construct your request body as shown.
Make sure to substitute the desired email address for {EMAIL_ADDRESS} and the product ID associated with the permission profile you wish to delete for {PRODUCT_ID}. These values can be taken from the response of the previous step.
Step 5. Call the Docusign Admin API
Now that you have constructed your request body, make a DELETE request to the MultiProductUserManagement:removeUserProductPermission endpoint to delete a product permission profile from the specified user. Please read the warning about using this endpoint.
Here’s how you make the call, but make sure to substitute your base path for {BASE_PATH}, your API account ID for {API_ACCOUNT_ID}, and your organization ID for {ORGANIZATION_ID}.
Expected response
If you run this code example from our Quickstart or launcher projects, you should see a JSON response similar to “Sample successful response”. “Sample failed response” is shown in the second gist tab.
Next steps
- Run this code example from our Quickstart or launcher projects: Bash, C#, Java, Node.js, PHP, PowerShell, Python, or Ruby.
- See all available Admin API How-to guides.
- See How to create a new active user for CLM and eSignature.
- See How to update user product permission profiles using an email address.
- See how to Go-Live with a completed app and find the base path for API calls in the production environment.