- Choose what Bridge governs. The default suits most organizations.
- Give people models: a Model Route for each client, allowed in Model Access.
- Give people tools: MCP servers and local tools, granted by a policy.
- Hand IT the values for the install.
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.What changes with Models only or MCP only
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.
- 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: it blocks the direct provider access these sessions need. Skip Give people models, and read Govern tools only (MCP only) 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 must allow it. Without both, launches fail.- 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.
- 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).
- Allow those routes in Model Access.
Billing people's Claude subscriptions
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.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 explains why. Create Claude routes sets up these fallbacks for you.

Which route each client needs
Which route each client needs
Give people tools
Barndoor refuses any tool that no policy grants, so each tool needs both steps:- Make the tool available.
- For services such as Jira, GitHub, or Salesforce, add an MCP server.
- 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.
- Grant it in a policy. See Manage policies. To have people approve a tool before each call, set it to Needs Approval; see Tool confirmations.
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.
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.
- Codex policy (on by default): it turns on Launch Codex Desktop and makes
codexwork only through Barndoor. Opt out if your fleet ships its own Codex requirements file. See 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.
- Scan tool calls for sensitive data, including tools that run on the laptop: MCP data protection policies.
- Sign in through your identity provider: Connect your IdP.
- Run your own MCP server on laptops: Publish a local MCP server.