Before you start
Your administrator must configure the integration and secure its credentials. Client secrets and webhook HMAC keys belong in approved secret storage, not documents or chat.
Step by step
- Open the DocuSign connection controls with the required administrator permission.
- Choose the intended environment. Use the sandbox for testing and the production environment for real signing.
- Start the connection and sign in to the intended DocuSign account. Review the consent before authorising.
- Return to Restore Intelligence and confirm the connected account and environment.
- Prepare a test draft and verify status handling before using the connection for a live agreement.
Agree connection ownership
Confirm account, environment and authorised integration owner. Distinguish who can connect the account from who can prepare/send envelopes. OAuth authorisation and webhook verification are separate controls; neither belongs in a shared document or browser-side setting.
Test the complete route
- Connect the intended sandbox account and check its recorded environment.
- Prepare an approved sample with test recipients.
- Complete an authorised signing test if required.
- Verify returned status and completed documents against the same envelope.
Maintain the connection
If authorisation is revoked or tokens fail, inspect connection state before reconnecting. Check account/environment instead of rotating unrelated HMAC keys. Escalate status problems with envelope reference and time, never secrets or access tokens.
What happens next
The connection is intended to persist. Reconnection may be needed after revocation or token problems; a new HMAC key should not be required for every envelope.
If something does not look right
If prompted repeatedly, check the recorded connection status and account/environment. Webhook verification and OAuth account authorisation serve different purposes; ask your administrator to inspect the configuration rather than rotating keys on each attempt.