How to Use the Ideas Feature
What you need to know about Docusign Community IdeasThis guide will walk you through the process of sharing your ideas, voting on existing ideas, and...
22860
Want to shape the future of Docusign? Add your ideas for dream features and upvote others you love.
Currently, when using Step Update Security, it is only possible to add security groups or users. However, there is no option to remove an existing user or explicitly set their permission to No Access.In our use case, we want to apply security to a specific folder and ensure that the CLM user does not have access. With the current functionality, the CLM user cannot be removed or restricted through Step Update Security, which limits our ability to properly control folder permissions.Requested enhancement: Allow removal of existing users/groups when using Step Update Security. Allow explicitly setting “No Access” for a specific user (e.g., CLM user group). Enable administrators to fully control folder-level security through the step configuration. Benefit:This enhancement would provide more flexible and complete security management, allowing administrators to ensure that unwanted users (such as CLM system users) can be removed or restricted when configuring folder permissions. Use CaseWhen the workflow creates a new supplier folder and the “Finance” subfolder, the security settings must be automated so that only the “Finance Security” group has access.To meet confidentiality requirements, access for default groups (for example, the “CLM User” group) must be removed so that these users cannot view the folder.Current Platform BehaviorBased on the current platform design, the Update Security step in a CLM workflow is additive only. This means it can grant permissions to additional users or groups, but it cannot remove existing permissions, remove inherited permissions, or set a group's access level to “No Access.”
ProblemIf Auto Renewal = Yes, the CLM system still requires manual or workflow-driven updates to: Extend the End Date Create the next renewal reminder Introduce native Auto Renewal logic in CLM:When: Auto Renewal = Yes The system should automatically: Extend the End Date based on the renewal term (e.g., +12 months). Create a new reminder based on the configured notice period. Repeat this process for each renewal cycle unless Auto Renewal is disabled.
We’d like to have 2 envelope custom fields (Document Type and Document Sub-Type) to create a 2-level classification hierarchy for our envelopes. We’d like the values available in the Document Sub-Type field to be dependent on which value was selected for Document Type. i.e. the options available in the second field should be dependent on which option was selected in the first field.This functionality would mirror what we have in Salesforce for classifying documents (dependent picklist fields), and we would like to map the Envelope Custom Fields to the corresponding fields in Salesforce. We would like users to be able to select valid combinations of Type and Sub-Type when sending an envelope via Docusign, and to have these updated back into Salesforce, so that documents sent via Docusign are classified/categorised according to the same schema as those which are sent from inside Salesforce.We would also like to be able to control the order in which these fields are displayed when sending an envelope. At the moment they are displayed in alphabetical order, which means the user thinks they are supposed to select a Document Sub-Type before they select a Document Type. We would like to be able to show these fields in the correct order, especially if the values in the second field are dependent on the value selected in the first field.
We are currently integrating DocuSign Real Estate Rooms into the Rialty.ai platform and are looking for a method to programmatically link a user’s NAR ID with their Rooms account.Providing this integration is a priority for us to ensure a seamless experience for our mutual customers. Could you please provide documentation or details regarding the available APIs or technical methods required to achieve this integration?
Using a drop down in a template, I would like to be able to enable/disable checkboxes in a group. There are multiple strategies in my dropdown list which would enable a single checkbox in another section. We currently only allow a 1-to-1 relationship.
Hello,We have a use case regarding the “Needs to View” option in DocuSign. In our process, we always include one person as a contract reviewer first, and then, in step two, the person who needs to sign the contract.The challenge is that with the current “Need to View” setting, the reviewer can only see the contract, and the document automatically continues to the signer afterward.However, in some cases, the reviewer may not agree with the content and would need to stop the contract from being sent forward.What we would really need is an enhanced option — something like a “Reviewer (View + Block if needed)” role. This would allow the reviewer to either let the contract proceed or block the workflow after their review.Thank you for taking this idea into consideration.Best regards,Marie
allow SCIM managed users to be able to manage DocuSign user profile attributes, such as Address, Company'' posted it as well in the DocuSign Community
Custody Transfer is currently only available for all envelopes sent from a user which does not help for companies that have admins that build different workflows and functionality that sending users use and manage once sent. Would like to see an option where you can set a custody transfer rule by user and subject line or template to better assist with these options. Or have the functionality within workflows when they start from a link which user the envelopes are sent from so it is not sent always from the admin accoun.t





Docusign Community
Code of ConductAlready have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.