# Roll Out Dtwo in Grok Bot

Roll out your Dtwo gateway to everyone in your organization in Grok Bot.

## Overview

This guide walks you through rolling out Dtwo to your whole organization in Grok Bot and turning off direct connections to MCP servers. If you only want to set it up for yourself, see [Connect Grok Bot for yourself](/docs/connect-yourself-grok-bot).

Grok Bot can't push a connector to everyone in your organization, so each person adds the gateway themselves. What admins can do, on the Enterprise plan, is allow only the gateway, which turns off direct connections to MCP servers. Grok Bot uses your team's settings in the [Cursor dashboard](https://cursor.com/dashboard), so you need admin access to your team there.

## Roll out Dtwo to your organization in Grok Bot

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: Have everyone in your organization add the gateway</p>

Grok Bot doesn't have a way to push a connector to everyone, so each person adds the gateway themselves by following [Connect Grok Bot for yourself](/docs/connect-yourself-grok-bot). Share that page with your team, along with your gateway's MCP URL. Copy it from your gateway's **Overview** tab in the Dtwo UI.

<p class="doc-step">Step 2: Turn off direct connections to MCP servers</p>

For the Enterprise plan. Grok Bot follows your team's connector policy in the [Cursor dashboard](https://cursor.com/dashboard), and the MCP allowlist blocks every server that doesn't match an entry on it.

1. In the [Cursor dashboard](https://cursor.com/dashboard), open your team settings and go to **MCP Configuration**.
2. Add one URL entry with your gateway's MCP URL, and leave its tools field empty so every tool is allowed. Copy the URL from your gateway's **Overview** tab in the Dtwo UI. It must start with `https://`.
3. Save the allowlist.
4. Open **Plugins & MCPs** and turn off the connectors in your Team Marketplace, so people can't connect apps directly. Members see them as **Disabled by team admin**.
5. If your team uses a Grok Bot network policy, open the **Grok Bot** page in the Cursor dashboard, go to **Network**, and add your gateway's host under **Allowed destinations**. Then turn on **Apply to MCP servers**, so the network policy also covers remote MCP servers. It's off by default.

Changes can take about a minute to apply. Ask people to restart the Grok Bot app afterward.

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

1. Open **Connect apps** and confirm your gateway is listed as connected.
2. In a chat, type `@` and attach your gateway, then ask which tools it has. It should list the tools from the MCP servers behind your gateway.
3. If you turned off other connectors, try adding a different custom MCP server. Grok Bot won't save it.

</div>

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

<p class="doc-step">Step 1: Get Grok Bot's client ID and secret from Microsoft Entra ID</p>

If you've already registered Grok Bot as an app in Microsoft Entra ID, go to **App registrations** and open the Grok Bot app. Copy the **Application (client) ID** from its **Overview** page — this is your `<ClientId>`. You'll also need the client secret you created when you registered it — this is your `<ClientSecret>`. If you no longer have it, create a new one under **Certificates & secrets**.

If you haven't registered Grok Bot in Microsoft Entra ID yet, follow [Register Grok Bot in Microsoft Entra ID](/docs/register-grok-bot-entra), then come back here.

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

Grok Bot doesn't have a way to push a connector to everyone, so each person adds the gateway themselves by following [Connect Grok Bot for yourself](/docs/connect-yourself-grok-bot). Share that page with your team, along with these three values, since most people can't look them up in your identity provider or the Dtwo UI themselves:

- **Client ID:** the client ID from Step 1.
- **Client secret:** the client secret from Step 1. Share it the way you share other credentials, not in a public channel.
- **Gateway URL:** your gateway's MCP URL. Copy it from your gateway's **Overview** tab in the Dtwo UI.

<p class="doc-step">Step 3: Turn off direct connections to MCP servers</p>

For the Enterprise plan. Grok Bot follows your team's connector policy in the [Cursor dashboard](https://cursor.com/dashboard), and the MCP allowlist blocks every server that doesn't match an entry on it.

1. In the [Cursor dashboard](https://cursor.com/dashboard), open your team settings and go to **MCP Configuration**.
2. Add one URL entry with your gateway's MCP URL, and leave its tools field empty so every tool is allowed. Copy the URL from your gateway's **Overview** tab in the Dtwo UI. It must start with `https://`.
3. Save the allowlist.
4. Open **Plugins & MCPs** and turn off the connectors in your Team Marketplace, so people can't connect apps directly. Members see them as **Disabled by team admin**.
5. If your team uses a Grok Bot network policy, open the **Grok Bot** page in the Cursor dashboard, go to **Network**, and add your gateway's host under **Allowed destinations**. Then turn on **Apply to MCP servers**, so the network policy also covers remote MCP servers. It's off by default.

Changes can take about a minute to apply. Ask people to restart the Grok Bot app afterward.

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

1. Open **Connect apps** and confirm your gateway is listed as connected.
2. In a chat, type `@` and attach your gateway, then ask which tools it has. It should list the tools from the MCP servers behind your gateway.
3. If you turned off other connectors, try adding a different custom MCP server. Grok Bot won't save it.

</div>

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

<p class="doc-step">Step 1: Get Grok Bot's client ID and secret from Okta</p>

If you've already registered Grok Bot as an app in Okta, go to **Applications and Resources → Applications** and open the Grok Bot app integration. On its **General** tab, copy the **Client ID** — this is your `<ClientId>` — and the **Client secret** — this is your `<ClientSecret>`.

If you haven't registered Grok Bot in Okta yet, follow [Register Grok Bot in Okta](/docs/register-grok-bot-okta), then come back here.

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

Grok Bot doesn't have a way to push a connector to everyone, so each person adds the gateway themselves by following [Connect Grok Bot for yourself](/docs/connect-yourself-grok-bot). Share that page with your team, along with these three values, since most people can't look them up in your identity provider or the Dtwo UI themselves:

- **Client ID:** the client ID from Step 1.
- **Client secret:** the client secret from Step 1. Share it the way you share other credentials, not in a public channel.
- **Gateway URL:** your gateway's MCP URL. Copy it from your gateway's **Overview** tab in the Dtwo UI.

<p class="doc-step">Step 3: Turn off direct connections to MCP servers</p>

For the Enterprise plan. Grok Bot follows your team's connector policy in the [Cursor dashboard](https://cursor.com/dashboard), and the MCP allowlist blocks every server that doesn't match an entry on it.

1. In the [Cursor dashboard](https://cursor.com/dashboard), open your team settings and go to **MCP Configuration**.
2. Add one URL entry with your gateway's MCP URL, and leave its tools field empty so every tool is allowed. Copy the URL from your gateway's **Overview** tab in the Dtwo UI. It must start with `https://`.
3. Save the allowlist.
4. Open **Plugins & MCPs** and turn off the connectors in your Team Marketplace, so people can't connect apps directly. Members see them as **Disabled by team admin**.
5. If your team uses a Grok Bot network policy, open the **Grok Bot** page in the Cursor dashboard, go to **Network**, and add your gateway's host under **Allowed destinations**. Then turn on **Apply to MCP servers**, so the network policy also covers remote MCP servers. It's off by default.

Changes can take about a minute to apply. Ask people to restart the Grok Bot app afterward.

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

1. Open **Connect apps** and confirm your gateway is listed as connected.
2. In a chat, type `@` and attach your gateway, then ask which tools it has. It should list the tools from the MCP servers behind your gateway.
3. If you turned off other connectors, try adding a different custom MCP server. Grok Bot won't save it.

</div>

</div>

---

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