# Roll Out Dtwo in Claude Desktop

Roll out your Dtwo gateway to everyone in your organization in Claude Desktop.

## Overview

This guide walks you through rolling out Dtwo to your whole organization in Claude Desktop and turning off every other connector. If you only want to set it up for yourself, see [Connect Claude Desktop for yourself](/docs/connect-yourself-claude-desktop).

Rolling out Dtwo to your organization needs a Claude Team or Enterprise plan and Owner access.

## Roll out Dtwo to your organization in Claude Desktop

Select how your gateway signs people in.

<div class="doc-tabs" data-tabs>

<div class="doc-tablist doc-tablist-cards" role="tablist" aria-label="Sign-in type">
<button type="button" role="tab" class="doc-tab" data-tab="dtwo" aria-selected="true"><img src="/favicon.svg" alt="" width="36" height="36" data-no-lightbox>Dtwo authentication</button>
<button type="button" role="tab" class="doc-tab" data-tab="entra"><img src="/logos/azure.svg" alt="" width="36" height="36" data-no-lightbox>Microsoft Entra ID</button>
<button type="button" role="tab" class="doc-tab" data-tab="okta"><img src="/logos/okta.png" alt="" width="36" height="36" data-no-lightbox>Okta</button>
</div>

<div class="doc-tabpanel" data-panel="dtwo" role="tabpanel">

<p class="doc-step">Step 1: Add the gateway for everyone in your organization</p>

You need to be an Owner, or on Enterprise, have a custom role that manages the organization's libraries.

1. Go to **Organization settings → Connectors**.
2. Click **Add**, then **Custom**. If you're asked for a connector type, choose **Web**.
3. Enter your gateway's MCP URL. Copy it from your gateway's **Overview** tab in the Dtwo UI. It must start with `https://`.
4. Under **OAuth client**, leave **Use Claude's published identity** selected.
5. Click **Add**.

Your gateway now shows up for every member under **Customize → Connectors** with a **Custom** label. Each member still signs in once with their Dtwo account:

1. Open **Customize → Connectors** and find your gateway.
2. Click **Connect** and sign in when the browser opens.

<p class="doc-step">Step 2: Turn off every other connector</p>

Members can only use connectors the organization has added, so this comes down to removing the rest and blocking desktop extensions.

**Remove the other connectors**

1. Go to **Organization settings → Connectors**.
2. For every connector other than your gateway, open its menu and remove it.
3. On a Team plan, members can ask for directory connectors with a **Request** button. Instead of adding a requested connector in Claude, add that MCP server to your Dtwo gateway so people use it through Dtwo.

On Enterprise, you can go further with custom roles and set connectors or single tools to **Blocked** for specific groups. See Anthropic's guide to [custom roles](https://support.claude.com/en/articles/13930452-manage-custom-roles-on-enterprise-plans).

**Block desktop extensions**

Desktop extensions are MCP servers that run on each person's computer. To block them:

1. Go to **Organization settings → Connectors** and open the **Desktop** tab.
2. Turn on **Allowlist** and leave the list empty.

This removes extensions people already installed and stops new ones from being installed. Requires Claude Desktop 0.13.91 or later.

<p class="doc-step">Step 3: Check the rollout</p>

1. In a new chat, ask Claude which tools it has through your gateway. It should list the tools from the MCP servers behind your gateway.
2. If you turned off other connectors, sign in as a member and open **Customize → Connectors**. Your gateway is the only connector listed. With desktop extensions turned off, **Settings → Extensions** doesn't appear.

</div>

<div class="doc-tabpanel" data-panel="entra" role="tabpanel">

<p class="doc-step">Step 1: Get Claude Desktop's client ID from Microsoft Entra ID</p>

If you've already registered Claude Desktop as an app in Microsoft Entra ID, go to **App registrations**, open the Claude Desktop app, and copy the **Application (client) ID** from its **Overview** page. This is your `<ClientId>`.

If you haven't registered Claude Desktop in Microsoft Entra ID yet, follow [Register Claude Desktop in Microsoft Entra ID](/docs/register-claude-desktop-entra), then come back here.

<p class="doc-step">Step 2: Add the gateway for everyone in your organization</p>

You need to be an Owner, or on Enterprise, have a custom role that manages the organization's libraries.

1. Go to **Organization settings → Connectors**.
2. Click **Add**, then **Custom**. If you're asked for a connector type, choose **Web**.
3. Enter your gateway's MCP URL. Copy it from your gateway's **Overview** tab in the Dtwo UI. It must start with `https://`.
4. Under **OAuth client**, choose **Use your own OAuth client** and enter the `<ClientId>` you registered with your identity provider.
5. Click **Add**.

Your gateway now shows up for every member under **Customize → Connectors** with a **Custom** label. Each member still signs in once with their own account:

1. Open **Customize → Connectors** and find your gateway.
2. Click **Connect** and sign in when the browser opens.

<p class="doc-step">Step 3: Turn off every other connector</p>

Members can only use connectors the organization has added, so this comes down to removing the rest and blocking desktop extensions.

**Remove the other connectors**

1. Go to **Organization settings → Connectors**.
2. For every connector other than your gateway, open its menu and remove it.
3. On a Team plan, members can ask for directory connectors with a **Request** button. Instead of adding a requested connector in Claude, add that MCP server to your Dtwo gateway so people use it through Dtwo.

On Enterprise, you can go further with custom roles and set connectors or single tools to **Blocked** for specific groups. See Anthropic's guide to [custom roles](https://support.claude.com/en/articles/13930452-manage-custom-roles-on-enterprise-plans).

**Block desktop extensions**

Desktop extensions are MCP servers that run on each person's computer. To block them:

1. Go to **Organization settings → Connectors** and open the **Desktop** tab.
2. Turn on **Allowlist** and leave the list empty.

This removes extensions people already installed and stops new ones from being installed. Requires Claude Desktop 0.13.91 or later.

<p class="doc-step">Step 4: Check the rollout</p>

1. In a new chat, ask Claude which tools it has through your gateway. It should list the tools from the MCP servers behind your gateway.
2. If you turned off other connectors, sign in as a member and open **Customize → Connectors**. Your gateway is the only connector listed. With desktop extensions turned off, **Settings → Extensions** doesn't appear.

</div>

<div class="doc-tabpanel" data-panel="okta" role="tabpanel">

<p class="doc-step">Step 1: Get Claude Desktop's client ID from Okta</p>

If you've already registered Claude Desktop as an app in Okta, go to **Applications and Resources → Applications**, open the Claude Desktop app integration, and copy the **Client ID** from its **General** tab. This is your `<ClientId>`.

If you haven't registered Claude Desktop in Okta yet, follow [Register Claude Desktop in Okta](/docs/register-claude-desktop-okta), then come back here.

<p class="doc-step">Step 2: Add the gateway for everyone in your organization</p>

You need to be an Owner, or on Enterprise, have a custom role that manages the organization's libraries.

1. Go to **Organization settings → Connectors**.
2. Click **Add**, then **Custom**. If you're asked for a connector type, choose **Web**.
3. Enter your gateway's MCP URL. Copy it from your gateway's **Overview** tab in the Dtwo UI. It must start with `https://`.
4. Under **OAuth client**, choose **Use your own OAuth client** and enter the `<ClientId>` you registered with your identity provider.
5. Click **Add**.

Your gateway now shows up for every member under **Customize → Connectors** with a **Custom** label. Each member still signs in once with their own account:

1. Open **Customize → Connectors** and find your gateway.
2. Click **Connect** and sign in when the browser opens.

<p class="doc-step">Step 3: Turn off every other connector</p>

Members can only use connectors the organization has added, so this comes down to removing the rest and blocking desktop extensions.

**Remove the other connectors**

1. Go to **Organization settings → Connectors**.
2. For every connector other than your gateway, open its menu and remove it.
3. On a Team plan, members can ask for directory connectors with a **Request** button. Instead of adding a requested connector in Claude, add that MCP server to your Dtwo gateway so people use it through Dtwo.

On Enterprise, you can go further with custom roles and set connectors or single tools to **Blocked** for specific groups. See Anthropic's guide to [custom roles](https://support.claude.com/en/articles/13930452-manage-custom-roles-on-enterprise-plans).

**Block desktop extensions**

Desktop extensions are MCP servers that run on each person's computer. To block them:

1. Go to **Organization settings → Connectors** and open the **Desktop** tab.
2. Turn on **Allowlist** and leave the list empty.

This removes extensions people already installed and stops new ones from being installed. Requires Claude Desktop 0.13.91 or later.

<p class="doc-step">Step 4: Check the rollout</p>

1. In a new chat, ask Claude which tools it has through your gateway. It should list the tools from the MCP servers behind your gateway.
2. If you turned off other connectors, sign in as a member and open **Customize → Connectors**. Your gateway is the only connector listed. With desktop extensions turned off, **Settings → Extensions** doesn't appear.

</div>

</div>

---

Having trouble? Email [support@dtwo.ai](mailto:support@dtwo.ai).