Skip to main content
Claude starts delivering work before you connect anything. On Slack content alone, it can catch a team up on a channel or thread, triage a request channel, turn a discussion into a doc, and track a project from channel history. Connections multiply what it can do from there; each one adds a system Claude can act in beyond Slack.

​
Your first Access bundle

An Access bundle is a named set of credentials, domain entries, repository grants, plugins, and instructions that Claude uses in the channels the bundle covers. A connection is one service credential inside a bundle, like a Datadog API key or a warehouse service account, that Claude uses to act in that service from any channel under the bundle’s scope. If you’re in setup, you add these connections there; skip to Decide what to connect. The steps below are for creating a bundle outside setup, on the admin page directly.
1

Open the admin page

Go to claude.ai/admin-settings/claude-tag. Under Claude Tag’s access, the Slack tab lists your scopes: Default Slack (organization-wide), then each workspace and any channels under them. Selecting Default Slack opens the Default Slack access panel.
2

Create a bundle on a scope

On the scope where you want the bundle to apply, click + next to Access bundles and choose Create new bundle. This creates the bundle and attaches it to that scope in one step; the bundle dialog opens.
3

Name the bundle

A bundle created on a workspace or channel scope is named after that scope, like Acme bundle for a workspace named Acme or #engineering bundle for that channel. A bundle created on Default Slack is named Untitled access bundle until you rename it. To rename a bundle, click the pencil next to the name (the console uses “profile” and “Access bundle” interchangeably).
You can also create an unattached bundle by clicking Create on the Access bundles page in the left navigation, then attach it to scopes afterward. A bundle created there is named Untitled access bundle until you rename it. Connections belong to the agent identity, not to any person. Personal claude.ai connectors apply in DMs. In organizations where personal connectors in channels is available, Claude can also use a member’s own connectors in a channel for that member’s own tasks, after the member allows it. Name a bundle after what it grants, since the name is what you’ll read when deciding which bundles to bind to a channel: data-readonly, github-write, monitoring, gtm-tools. A capability name stays meaningful when the same bundle serves several teams; a team name (devprod-team) works when one team’s full access is the unit you’ll reuse.

​
Why create more than one bundle

Multiple bundles let you grant access by capability and compose it per channel. For example, with separate data-readonly, github-write, and monitoring bundles: #platform-eng gets all three, #gtm-analytics gets only data-readonly, and #incidents gets monitoring plus github-write. Each credential is defined once, so rotating a Datadog key means editing one bundle without touching the others. A bundle also has Domains, Plugins, and Instructions tabs alongside Credentials and Repositories. Use the bundle’s Instructions for guidance that should travel with a credential; use per-scope custom instructions for guidance tied to a place.

​
Decide what to connect

Six categories cover most of the work teams hand to Claude. Any service with an HTTP API can be added; start with the categories that match what your teams already do. Read-only connections are most useful in combination: an answer that joins the ticket, the deploy, and the error rate needs all three systems connected. Connecting many systems read-only is a different decision from granting write access anywhere. Per-service instructions, with the credential fields and allowed-websites values, are in the connection guides.

​
Create a dedicated account per service

The credential you connect is Claude’s account in that tool, not yours. Anyone in a channel under the bundle’s scope can use it through Claude, so connect a dedicated identity you control rather than your personal login.
For each tool, create that identity specifically for the agent rather than reusing a shared bot key. The pattern depends on the service. A dedicated account keeps the agent’s activity separately auditable in each tool’s logs and lets you revoke its access without touching anyone else’s. Grant read-only wherever the categories below say read; Claude can never exceed what the key allows. If the person who administers a service isn’t you, send them this:

​
Limit access to specific resources

A connection has no setting for which pages, folders, or projects Claude can reach inside a tool. The connection’s reach is whatever the connected account can access in that tool. To narrow Claude to a subset, narrow the account:
  • Confluence or another wiki: give the service account read access to only the spaces or pages Claude should see
  • Google Drive: share only the relevant folders with the dedicated Google account; see Google Workspace
  • Project or ticket trackers: add the service account to only the projects it needs
The host, path, and method restrictions on a connection control which API endpoints Claude can call, not which records those endpoints return. Use them alongside account-level scoping, not instead of it. For a shared or external channel, put the narrowed connection in its own bundle and attach that bundle only to that channel, so the credential is unavailable elsewhere.

​
Connect a service that isn’t in the list

The services with Connect buttons on the Credentials tab are presets, not the full set Claude can connect to. Any app with an API can be connected: click Connect next to Custom tool at the bottom of the tab. See the Custom connection guide for the form fields, credential types, and how to add a custom MCP server. You can also add connections from a channel’s Configure page. The option to add one appears there only for people who can manage Claude’s setup for that channel or for the whole organization. Channel managers can manage setup for their assigned channels. Other channel members see the channel’s connections on the Configure page but can’t add one.

​
Allow a host without a credential

Claude does channel work in an isolated sandbox. A network request is traffic that sandbox sends to a host, such as an API call, a curl fetch, or a package install. Before Claude can make one from a channel, the destination host has to be allowed by one of three settings, the allow layers:
  • A domain entry: a hostname listed on this bundle’s Domains tab. Requests to it pass with no credential attached; see Add a domain.
  • A connection: a credential on this bundle’s Credentials tab. Requests matching its allowed websites pass with that credential attached.
  • The scope’s environment: the compute configuration the scope’s sessions run in, which carries its own network access setting, starting at the Trusted access level that covers common package registries. Requests to hosts it allows pass with no credential; see Broad web access through the environment.
A host that none of these allows stays unreachable, and when more than one bundle is attached to a scope, the entries of all of them apply. Web search is governed by none of them, because searching happens on Anthropic’s servers rather than in the sandbox; see Web search vs. network requests.

​
Add a domain

A domain entry allowlists one hostname for every channel this bundle covers. After you add it, requests from those channels’ sandboxes to that host go through with no credential attached. To get there, open the bundle from the scope that covers the channel, under Claude Tag’s access at claude.ai/admin-settings/claude-tag; if the scope has no bundle yet, create one first. On the bundle’s Domains tab, fill in the form and click Add domain:
  • Domain: the hostname to allow; a wildcard is allowed as the leftmost label, like *.example.com, and covers subdomains at any depth but not example.com itself
  • Ports: needed only when the service listens on something other than 443
For example, to let Claude check a vendor’s status page at status.example.org, enter status.example.org in the Domain field and leave the Ports field empty. You don’t have to predict the full list up front. When a request is blocked, Claude says so in the thread and names the host, with wording like “blocked by the network egress proxy” (that is, by Agent Proxy); add that host here and retry. If the host is listed and Claude still reports it blocked, check these in order:
  • The bundle is attached to the channel’s scope. Claude can use a Domains entry only in channels whose scope, or an ancestor scope, has this bundle attached; see Attach bundles to scopes.
  • The entry matches the exact host. A wildcard like *.example.com doesn’t cover example.com itself, and www.example.com and example.com are different hosts.
  • The request didn’t move to another host. If the page redirects, or loads from a CDN or a sign-in host, allow that host too; Claude names the host it was blocked on.
  • The port is listed. Needed only when the service listens on something other than 443.
  • A minute has passed since you saved the entry. Agent Proxy picks up a new entry within about a minute, in existing threads as well as new ones, so retry in the same thread after a short wait.
  • The bundle was attached before the thread started. A bundle you attach after a thread started isn’t guaranteed to reach that thread, so start a fresh thread to use its entries.
  • The request came from a channel, not a DM. A bundle attached to a channel doesn’t apply in DMs.
Typical entries are hosts the work calls without a key, such as a docs site or a public API. Common package registries are usually already reachable through the environment’s Trusted access default, and a host that needs a credential belongs in a connection instead. Entries appear below the form, and each one can be edited or removed from its row.
Agent Proxy carries only HTTP and HTTPS. A protocol that isn’t HTTP, such as SSH, can’t cross the proxy, so listing a host here doesn’t make it reachable over SSH.

​
Broad web access through the environment

Domain entries allow hosts one at a time. For a scope whose work needs more of the web, the environment setting grants broader access. An environment is the sandboxed compute configuration the scope’s sessions run in, and it carries its own network access setting. A new environment’s network access level is Trusted access, which allows a documented set of package registries and developer hosts. A channel can already reach hosts like pypi.org and registry.npmjs.org with no domain entry. To give a scope broader access, create an organization-shared environment with a more permissive level and set it on the scope, as described in Configure the environment for a scope. Full access allows any domain; see Network access in the Claude Code docs for the other levels.

​
Allow all hosts

Allow-all egress is off by default; ask your Anthropic account team to enable it for your organization. Once enabled, you can enter * alone as the domain. A * entry needs ports assigned; it admits any host on those ports, with no credential attached. With * active:
  • Requests to hosts that no connection covers go through with no credential attached.
  • A * entry never carries a credential, and a connection’s credential still travels only to its allowed websites.
  • Private and internal network addresses and cloud metadata endpoints remain blocked.
Without allow-all egress enabled, saving * fails with a generic “Couldn’t add domain.” error that doesn’t name the cause. If the capability is later disabled, you can disable an existing * entry or narrow it to specific hosts, but you can’t keep it active.

​
Web search vs. network requests

Web search needs no domain entry, connection, or environment setting. It’s Anthropic’s built-in web search tool, and the searching happens on Anthropic’s servers rather than in the channel’s sandbox, so no allow layer applies. Opening a page is not part of the search. A search returns content from the pages it matches, which Claude reads and cites; fetching a URL from the sandbox is a network request like any other, and the host needs an allow layer. Claude can answer from a page that search surfaced yet report that it can’t open the same link. If the work needs Claude to open and read pages rather than answer from search results, allow those hosts through the settings above. Web search vs. network requests covers the session mechanics behind the split.

​
Add a connection

On the bundle’s Credentials tab, click Connect next to a listed service, or next to Custom tool for a service not in the list. For a custom connection, choose the credential type: For GitHub repositories, use the GitHub connection at Configure GitHub access rather than a credential from this table. Credentials are injected at the network boundary by Agent Proxy; the model and the sandbox are not given the key. A request to a host you haven’t allowed is blocked, not sent. See how Agent Proxy works. When someone else holds a service’s secret, create a setup link instead of collecting the secret yourself. On the service’s row in the Credentials tab, open the Connect button’s menu and select Copy link for another admin. Whoever opens the link signs in to your Claude organization and submits the credential there. They don’t need an admin role. The row tracks the link. It shows Pending until the credential is submitted, then Approval needed. Select Review to check the submission and approve or reject it. The credential becomes active only after you approve it. The row shows Expired for a link that went unused, and until the credential is submitted you can revoke the link from the row’s ⋮ menu. Setup links are available for services that use the Bearer or Basic credential type. For other types, the Connect menu has no link option.

​
Set allowed websites

List the hosts a connection’s credential may be sent to. A wildcard works only as the leftmost label, like *.example.com; it covers subdomains at any depth but not example.com itself. You can’t enter * alone here; a credential is always limited to specific hosts. To let Claude reach any host without a credential, see Allow all hosts. To change a connection’s name or allowed websites after saving, open the ⋮ menu on that connection’s row in the bundle’s Credentials tab and choose Edit; the Edit connection dialog labels the field Allowed hosts. The same menu has Rotate secret (where the credential type supports it) and Delete. Check the host against your account’s region before saving. Some presets fill a default host that may not match your account’s region; a Datadog key, for example, only works against your account’s Datadog site, like api.datadoghq.com or api.datadoghq.eu.

​
Restrict by path or method

After saving, you can narrow a connection. Select Edit on the connection’s row in the bundle’s Credentials tab. The Edit connection dialog lets you rename the connection and, where the connection has an allow rule, restrict it by HTTP method and path, for example to allow GET but not DELETE. Agent Proxy starts applying an edit to a connection or a Domains entry within about a minute after you save it, in existing threads as well as new ones. It evaluates connections and Domains entries from the most specific scope outward (channel, then workspace, then organization), and within a scope by priority; the first match decides. A request that matches no connection, no Domains entry, and nothing in the environment’s network access is blocked. Private IP ranges and cloud metadata endpoints stay blocked regardless.

​
Connections vs claude.ai connectors

The connection gallery lists credential types the agent can hold, not the connectors your organization or its members have set up on claude.ai. A connection authenticates the agent, not a person; a connector on someone’s personal claude.ai account doesn’t appear here. For Google services, use a service-account key or the MCP Connector sign-in option, both of which give the agent one credential with access to the data the channel needs. Personal connectors keep working in DMs.

​
Attach plugins

A connection grants access; a plugin teaches Claude how to use it well. A plugin is a packaged set of skills: reusable instructions for working with a specific tool or following a specific process. Attach a plugin to the same Access bundle or scope that carries the connection, so the credential arrives with directions for using it. A Datadog API key, for example, makes the API reachable, and a Datadog plugin tells Claude which endpoints answer which questions. Once you turn a plugin on for a bundle or add it to a scope, sessions in the channels that bundle or scope covers pick up the plugin automatically. Nobody in those channels has to turn that plugin on. A channel member can also add a plugin available to your organization, by asking Claude in the channel or from the channel’s Configure page, unless an admin has restricted editing to admins. Anthropic provides plugins for common tools and processes, and you can add your own from a skills repository. To give Claude organization-wide skills, package them as a plugin. Admins and channel members turn plugins on in different places:
  • A plugin added directly on a scope (the plugin chips on the scope’s panel) is enabled there as soon as you add it.
  • A bundle’s Plugins tab lists the plugins available to your organization, each off until you toggle it on.
  • A channel member can ask Claude to add a plugin to their channel, unless an admin has restricted editing to admins. Claude proposes the change and adds the plugin only after someone in that channel selects Confirm.
Adding a plugin for your whole organization makes it available, not active. The plugin takes effect only where a bundle enables it or a scope adds it directly. Adding or removing plugins and skills applies to new threads only. A thread already running keeps the set it began with; start a fresh thread to pick up changes. See What survives between replies. Claude can’t publish a new skill version from inside a thread; that update happens in admin settings.

​
Code review with the Security Guidance plugin

Anthropic’s Security Guidance plugin has Claude review the code it writes. With the plugin on in a channel, Claude is warned about risky patterns as it edits files, and the plugin reviews the code changes in the session’s repository when Claude commits, pushes, or finishes a reply, checking for vulnerabilities such as injection, cross-site scripting, and hardcoded secrets. Claude addresses the findings or reports them in the thread. Security Guidance is off by default. Add it directly on a scope, or turn it on in a bundle’s Plugins tab, and new threads in covered channels pick it up. The plugin flags problems and suggests fixes; it doesn’t block a commit or a push. To require review before code merges, use your repository’s branch protection and required checks.

​
Verify the connection saved

  • Each connection is listed in the bundle with the host you set.
  • The Access bundles page shows a status for each connection when you expand the bundle.
    • Active: Claude can send the credential to its allowed hosts
    • Not active: the secret is stored but no allow rule uses it yet, so Claude can’t send it.
    • Approval needed: another admin submitted the credential through a shared setup link. Select Review on its row, then Approve.
    • Used with a time, or Never used: when Claude last sent the credential; independent of the status
  • New threads pick up new connections on their own. An existing thread isn’t told about a connection added after it started, but the connection works there; ask Claude to use the service by name.