Electronic signature (DocuSign)

Send quotes for electronic signature using your own DocuSign account (BYO model).

The Electronic signature integration uses YOUR DocuSign account (BYO model: you bring your own account). Envelopes are created and billed in your DocuSign account: there is no cost, margin or intermediation on our side. We only wire up the fields and the button to send the quote for signature.

The integration starts inert: nothing happens until you fill in the fields and activate. The access token is stored encrypted in the CRM and is never displayed back.

Prerequisites

• A DocuSign account (demo/test or production environment) with permission to send envelopes.
• Access to the DocuSign dashboard to view Apps and Keys (Account ID and Base URI), generate an OAuth access token and configure DocuSign Connect (Admin → Connect).
• In Sellio, administrator access to save the credentials and activate the integration in Settings → Integrations.

What you need to fill in

• Account ID (API Account ID): the identifier of your DocuSign account, found under Settings → Apps and Keys in the DocuSign dashboard.
• Account Base URI: your account's base address, which is https://demo.docusign.net in the test environment, or something like https://na3.docusign.net in production (the subdomain varies by account; it appears on the same Apps and Keys screen).
• Access token (OAuth): an access token you generate in DocuSign to authorize the calls. It is stored encrypted in the CRM.
• Connect HMAC key (required to receive webhooks): the secret key DocuSign uses to sign every webhook. Enable HMAC under Admin → Connect and copy the generated key. Without it, webhooks are rejected (the signature status will not advance on its own).

How to configure

1. Open Settings → Integrations and find the "Electronic signature (DocuSign)" card.
2. Paste the Account ID, the Base URI, the Access token and the Connect HMAC key and click "Save credentials".
3. Copy the "Webhook URL (DocuSign Connect)" that appears and, in DocuSign Admin → Connect, create a custom configuration pointing to that URL, checking the envelope events (sent, delivered, completed, declined, voided).
4. In the same Connect configuration, ENABLE HMAC (Include HMAC signature) using the same key you pasted into the CRM. DocuSign then signs every event in the X-DocuSign-Signature-1 header and the CRM verifies it.
5. Return to the CRM and click "Activate".

How to send a quote for signature

1. Open an opportunity and go to the Quotes section.
2. On the desired version, click "Signature", enter the signer's email (and optionally name) and confirm.
3. The CRM creates an envelope in DocuSign with the quote document and sends the signature email to the signer.
4. As the signer progresses, the status appears in the quote's "Signatures" list (Sent → Delivered → Signed).

Today authentication uses an access token you paste (the simplest path). A future evolution is JWT grant (integration key + private key), which renews the token automatically without manual pasting.

How to test

1. Use the demo environment (Base URI https://demo.docusign.net) with a test access token.
2. On a quote, click "Signature", enter your own email as the signer and confirm.
3. Check that you received the DocuSign email and that the quote's "Signatures" list shows "Sent".
4. Sign the document; confirm the status advances (Delivered → Signed) and the quote is marked as accepted, a sign that DocuSign Connect reached the CRM.

Troubleshooting

• 401 when sending: the access token expired (DocuSign OAuth tokens are short-lived) or is wrong. Generate a new token and re-paste. The Account ID and the Base URI must be from the SAME account.
• Account/URL error: confirm the correct Base URI (demo.docusign.net in test; naX.docusign.net in production, where the subdomain appears in Apps and Keys) and the API Account ID.
• The status does not update on the quote: DocuSign Connect is not arriving OR the HMAC signature does not match. In Admin → Connect, confirm the configuration pointing to the "Webhook URL (DocuSign Connect)", with the envelope events and with HMAC enabled using the SAME key pasted into the CRM.
• Webhook rejected (invalid signature / no HMAC key): for security, the CRM only accepts signed webhooks. If the Connect HMAC key is not filled in the CRM, or differs from the one DocuSign uses, events are rejected. Align the same key on both sides and re-enable HMAC in Connect.
• The button does not appear / nothing happens: the integration is inert for lack of credentials or was not activated. Fill in the fields and click Activate.
• 404 on the Connect URL: the integration was deactivated or the URL token changed. Reactivate and reconfigure the URL in DocuSign.

Open this article inside the system →