Show Connect dependencies and warnings before deleting HMAC keys

We recently encountered an incident where an HMAC key was accidentally deleted from the DocuSign Admin configuration.

Although deleting the key itself was a simple administrative action, the impact was significant: several Connect integrations relying on that HMAC key could no longer successfully validate their webhook messages.

The main challenge was not only the accidental deletion, but also the lack of visibility into the dependencies. There was no clear overview showing which Connect configurations were using the deleted HMAC key, making it difficult and time-consuming to identify all impacted integrations.

I would suggest that DocuSign introduces the following safeguards:

• Show all Connect configurations using an HMAC key.
• Display an impact warning when attempting to delete a key that is still in use.
• Clearly identify the affected Connect configurations in that warning.
• Require explicit confirmation before deletion of an actively used key.
• Preferably prevent deletion until the HMAC dependency has been removed or replaced.
• Record HMAC creation/deletion and its dependencies in the administrative audit history.
• Consider a short soft-delete/recovery period for accidentally deleted keys.

For example:

Warning: This HMAC key is currently used by 3 active Connect configurations. Deleting it may cause webhook validation failures and interrupt these integrations.