Allow Dynamics Administrators to Control Which Dynamics 365 Entities Display DocuSign Log In/Log Out Commands

Today, DocuSign for Dynamics 365 allows administrators to configure which entities are enabled for DocuSign actions such as Sign, Send with DocuSign, and Bulk Send with DocuSign. However, the DocuSign Log In/Log Out ribbon commands (which I believe came as part of the move to OAuth) appear on entities that are not enabled for DocuSign use.

We would like an enhancement that gives administrators explicit control over where the Log In/Log Out commands are displayed, ideally leveraging the existing entity configuration experience within DocuSign Admin.

Suggested approaches:

1. Only display Log In/Log Out commands on entities that are enabled for DocuSign integration (e.g. Sign, Send, Bulk Send).
2. Alternatively, add a configurable setting per entity that controls Log In/Log Out visibility, similar to existing DocuSign command configuration options.

Business Value I would assume most organizations use DocuSign with only a subset of Dynamics 365 entities. Displaying Log In/Log Out commands across unrelated entities:

• Creates unnecessary ribbon clutter.
• Confuses users who will never use DocuSign.
• Introduces DocuSign-related processing on forms that have no DocuSign business purpose.
• Limits administrators' ability to tailor the user experience to their business processes.

Providing entity-level control would improve usability, reduce user confusion, and better align the DocuSign experience with how customers already configure entity-specific functionality in Dynamics 365.

Expected Outcome Administrators should be able to determine exactly which entities expose DocuSign authentication commands, resulting in a cleaner and more relevant Dynamics 365 experience for end users.