> 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 OAuth credentials for multiple accounts

> As a partner or integrator see how you can use your main account’s OAuth for Connect settings for each of your client 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 main account’s OAuth for Connect settings for each client. This lets you configure and enforce using OAuth security for each client Connect account without having to set up each one manually.

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

1. Set up the OAuth for Connect credentials in your main account.
2. Using an integration key from your main account, use the [ConnectConfigurations:createConnectOAuthConfig](/docs/esign-rest-api/reference/connect/connectconfigurations/createconnectoauthconfig) API request to create a new Connect configuration in the client’s account on their behalf.

   * Set the `includeOauth` and `integratorManaged` fields in the request body to `true`. This indicates that OAuth is required, and that the main account’s OAuth for Connect config values will be used.
   * The access token used for the API call will identify the main account whose OAuth 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 OAuth credentials will be used.

**`Example JSON SIM Connect configuration body`**

```json title="Example JSON SIM Connect configuration body"
{
    "configurationType":"custom",
    "urlToPublishTo":"Your Webhook URL",
    "name": "Your configuration name",
    "allowEnvelopePublish":"true",
    "enableLog":"true",
    "includeOauth":"true",
    "integratorManaged":"true",
    "deliveryMode":"SIM",
    "events":[
        "envelope-completed"
    ],
    "requiresAcknowledgement":"true"
}
```

This diagram shows the flow for how integrator-managed OAuth for Connect handles events and access tokens:

![Diagram showing the flow for how integrator-managed OAuth for Connect handles events and access tokens](/_fern-files/_img/79775d459424027c535b543179a6273a9faf429e10d1c211637addc4e9c508c7.webp)