> ## Documentation Index
> Fetch the complete documentation index at: https://docs.barndoor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up your organization for Bridge

> The four things a Barndoor admin sets up before IT installs Bridge: what Bridge governs, models, tools, and the values IT needs.

This page is for the Barndoor admin who gets an organization ready for Bridge. Do it before IT installs Bridge on any laptop: a laptop with nothing set up behind it signs in, then refuses to launch.

Most organizations need four steps:

1. [Choose what Bridge governs](#choose-what-bridge-governs). The default suits most organizations.
2. [Give people models](#give-people-models): a Model Route for each client, allowed in Model Access.
3. [Give people tools](#give-people-tools): MCP servers and local tools, granted by a policy.
4. [Hand IT the values for the install](#values-it-needs).

Everything else is [optional](#optional-settings).

## Choose what Bridge governs

Set this on the **Bridge governs** card at the top of **LLM Management → Client settings**. It applies to everyone in the organization from their next launch. Running sessions pick it up at their next hourly renewal, and a session the new setting can't serve stops working then. Leave it on **Models and MCP** unless you have a reason to change it.

| Option | Barndoor governs | Use it when |
| - | - | - |
| **Models and MCP** (default) | Model requests, through your LLM Gateway, and tool calls, through the Barndoor MCP server | You want both governed. |
| **Models only** | Model requests only | You govern models and cost, and handle tools another way. |
| **MCP only** | Tool calls only. People use their own Claude or OpenAI sign-in for models. | You govern tools and data, and people keep their own model access. |

> [accordion] What changes with Models only or MCP only
>
> * **Models only:** the **Servers** and **Policy** tabs disappear from the Bridge window. Client settings can't route Shell or Network **Through Barndoor**, because there's no Barndoor tool to route to; set them to **Native** or **Off**, or launches are refused. Skip [Give people tools](#give-people-tools).
> * **MCP only:** Model Access, model data protection, and LLM usage reporting don't apply, and client settings don't restrict the clients' own tools. Claude Desktop opens as the person's own Claude Desktop with the Barndoor MCP server added, and they can remove it. **Kilo can't launch**, because it runs only on Barndoor's models. **Don't turn on [provider lockdown](https://docs.barndoor.ai/how-tos/barndoor-bridge/provider-lockdown.md)**: it blocks the direct provider access these sessions need. Skip [Give people models](#give-people-models), and read [Govern tools only (MCP only)](https://docs.barndoor.ai/how-tos/barndoor-bridge/mcp-only.md) before you roll out.

## Give people models

Each client needs at least one enabled Model Route it can use, and each person's [Model Access](https://docs.barndoor.ai/how-tos/use-llm-controls.md#model-access) must allow it. Without both, launches fail.

1. **For Claude Code and Claude Desktop,** create Claude routes. If you have an Anthropic subscription provider, the quickest way is **Create Claude routes** on the Claude Code tab of **Client settings**; see [Create Claude routes](https://docs.barndoor.ai/how-tos/barndoor-bridge/models.md#create-claude-routes).
2. **For Codex and Kilo,** make sure at least one route doesn't use only Claude subscriptions, for example a GPT route on an OpenAI API key or on people's ChatGPT subscriptions ([Use Codex with the LLM Gateway](https://docs.barndoor.ai/how-tos/use-codex-with-llm-gateway.md)).
3. **Allow those routes** in [Model Access](https://docs.barndoor.ai/how-tos/use-llm-controls.md#model-access).

A route that resolves to no enabled model is the most common reason a first launch fails. The [LLM Gateway quickstart](https://docs.barndoor.ai/how-tos/llm-gateway-quickstart.md) has a curl test you can run before touching a laptop. [Models](https://docs.barndoor.ai/how-tos/barndoor-bridge/models.md) explains how each client chooses among the routes a person is allowed.

> [accordion] Billing people's Claude subscriptions
>
> Add the **Anthropic OAuth** provider from **LLM Management → Providers** (there's no API key to store) and attach it to a Model Route. See [Anthropic OAuth passthrough](https://docs.barndoor.ai/how-tos/llm-gateway-quickstart.md#step-1-add-provider-credentials).
>
> Put the subscription first on each Claude route and an API-key, Bedrock, Vertex, or Foundry target second, so Claude Desktop's background calls, Codex, and Kilo can use the route too. [Claude subscription routes](https://docs.barndoor.ai/how-tos/barndoor-bridge/models.md#claude-subscription-routes) explains why. **Create Claude routes** sets up these fallbacks for you.
>
> ![The Add a Provider card picker, with the Anthropic OAuth card at the right: Forward Claude Code OAuth bearer tokens to Anthropic while Barndoor authenticates requests with x-api-key](https://mintcdn.com/barndoor/C8Lw-cmuSCqc3Z7x/images/barndoor-bridge/anthropic-oauth-provider.png?fit=max\&auto=format\&n=C8Lw-cmuSCqc3Z7x\&q=85\&s=0a0791bc5a845a5b802f7e1a5ea9d059)

> [accordion] Which route each client needs
>
> | Client | Route it needs |
> | - | - |
> | **Claude Code** | A Claude route. It can bill each person's Claude subscription (the **Anthropic OAuth** provider) or an API key, Bedrock, Vertex, or Foundry. |
> | **Claude Desktop** | A Claude route. Conversations work on a Claude subscription, but give the route an API-key, Bedrock, Vertex, or Foundry target too, so Claude Desktop's connection check and chat titles work. |
> | **Codex CLI and Codex Desktop** | Any route or routing policy that isn't Claude-subscription-only. A GPT route can bill an OpenAI API key or each person's ChatGPT subscription (the **OpenAI Codex OAuth** provider). |
> | **Kilo** | Any route that isn't Claude-subscription-only, including routes on a ChatGPT subscription. |

## Give people tools

Barndoor refuses any tool that no policy grants, so each tool needs both steps:

1. **Make the tool available.**
   * For services such as Jira, GitHub, or Salesforce, [add an MCP server](https://docs.barndoor.ai/how-tos/add-an-mcp-server.md).
   * For tools that run on each person's laptop, such as Shell, Filesystem, Git, and AWS CLI, turn on Bridge's built-in local servers. They start switched off. See [Local MCP servers](https://docs.barndoor.ai/how-tos/barndoor-bridge/local-mcp-servers.md).
2. **Grant it in a policy.** See [Manage policies](https://docs.barndoor.ai/how-tos/manage-policies.md). To have people approve a tool before each call, set it to **Needs Approval**; see [Tool confirmations](https://docs.barndoor.ai/how-tos/tool-confirmations.md).

People then connect the servers they want in **My Apps**, unless you made a server available to everyone.

## Values IT needs

Give IT these before they render the install profiles. Re-rendering later reissues the profiles, so get them right the first time.

| Value | Where to find it |
| - | - |
| **Organization slug** | Click your name at the bottom of the left-hand nav. The slug is under your email, for example `barndoor-ai`. |
| **Backend URL** | `https://app.barndoor.ai/api` for production. |

IT will also ask about two decisions:

* **Provider lockdown** (off by default): whether to block direct access to LLM provider APIs on macOS, so Claude runs only through Barndoor. See [Provider lockdown](https://docs.barndoor.ai/how-tos/barndoor-bridge/provider-lockdown.md).
* **Codex policy** (on by default): it turns on **Launch Codex Desktop** and makes `codex` work only through Barndoor. Opt out if your fleet ships its own Codex requirements file. See [Codex policy](https://docs.barndoor.ai/how-tos/barndoor-bridge/provider-lockdown.md#codex-policy).

## Optional settings

None of these is needed for a first launch:

* **Restrict the clients' own tools** (files, shell, web, browser), which are all on by default: [Client settings](https://docs.barndoor.ai/how-tos/barndoor-bridge/client-settings.md).
* **Scan tool calls** for sensitive data, including tools that run on the laptop: [MCP data protection policies](https://docs.barndoor.ai/how-tos/data-control-center/mcp-policies.md).
* **Sign in through your identity provider:** [Connect your IdP](https://docs.barndoor.ai/how-tos/idp-setup.md).
* **Run your own MCP server on laptops:** [Publish a local MCP server](https://docs.barndoor.ai/how-tos/barndoor-bridge/publish-local-mcp.md).

## Next

IT installs Bridge: [Install on macOS](https://docs.barndoor.ai/how-tos/barndoor-bridge/install-with-mdm.md) or [Install on Windows](https://docs.barndoor.ai/how-tos/barndoor-bridge/install-on-windows.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.