> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# Managing HMAC for multiple accounts

> As a partner or integrator with one main account who must manage multiple client connect accounts, you can configure your client accounts to be integrator managed, enabling you to use your HMAC keys for your clients’ event messages.

As a partner or integrator with one main account who must manage multiple client connect accounts, you can configure your client accounts to be *integrator managed*, enabling you to use your HMAC keys for your clients’ event messages. This lets you configure and use your HMAC security settings for each client Connect account without having to set up each one manually.

This diagram shows the flow for how integrator-managed HMAC for Connect handles events.

To set up a client Connect configuration that uses your main account’s existing HMAC settings:

1. Set up the HMAC for Connect credentials in your main account. See [How to set up HMAC security with your app](/platform/webhooks/connect/setting-up-hmac) for a full walkthrough.
2. Using an integration key from your main account, use the [ConnectConfigurations:create](/docs/esign-rest-api/reference/connect/connectconfigurations/create) API request to create a new Connect configuration in the client’s account on their behalf.

   * Set the `includeHMAC` and `integratorManaged` fields in the request body to true. This indicates that HMAC is required, and that the main account’s HMAC for Connect configuration values will be used.
   * The access token used for the API call will identify the main account whose HMAC for Connect settings will be used.

     **Note:** Envelope- and account-level Connect configurations can be set to be integrator-managed, but they can only currently be configured using the API.
3. When an Connect event notification is generated by an action taken in the customer’s account, the main account’s HMAC credentials will be used.

![Diagram showing the HMAC for partners flow](/_fern-files/_img/a97447b1c64e46a47d71b2925bf6e55644cdc7395e40011dd388f9a06695bd7a.webp)

The following sample payload shows how the `integratorManaged` parameter looks:

```text
{
    "configurationType": "custom",
    "urlToPublishTo":"Your Webhook URL",
    "allUsers": "true",
    "name": "Your configuration name",
    "allowEnvelopePublish": "true",
    "enableLog": "true",
    "includeHMAC": "true",
    "integratorManaged": "true",
    "deliveryMode": "SIM",
    "events": [
        "envelope-completed"
    ],
    "eventData": {
        "version": "restv2.1",
        "includeData": [
            "tabs",
            "payment_tabs",
            "custom_fields",
            "powerform",
            "recipients",
            "folders",
            "extensions",
            "attachments",
            "prefill_tabs",
            "document_fields"
        ]
    },
    "requiresAcknowledgement": "true"
}
```

## Next steps

* [How to set up HMAC security with your app](/platform/webhooks/connect/setting-up-hmac)
* [Partner implementation overview](/partner/partner-implementation-overview)
* [Managing OAuth credentials for multiple accounts](/platform/webhooks/connect/validation-and-security/managing-oauth-credentials-multiple-accounts)