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

# Tenant vs. Personal Level Gateway Configs

> Choose Personal or Tenant visibility for an MCP Gateway, and control who can see, use, and edit it.

Every MCP Gateway has one of two visibility levels: **Personal** or **Tenant**. This setting controls who can see the Gateway and who can use it. Any user can create a Personal Gateway for their own use. Creating, editing, and deleting a Tenant Gateway is restricted to the **Platform Admin** and **Security Admin** roles.

## The two models

|                               | Personal                                                        | Tenant                             |
| ----------------------------- | --------------------------------------------------------------- | ---------------------------------- |
| **Who can see it**            | Only the creator                                                | Everyone in the organization       |
| **Who can use it**            | Only the creator                                                | Everyone in the organization       |
| **Who can edit or delete it** | Only the creator                                                | Platform Admin or Security Admin   |
| **Who can create one**        | Any user                                                        | Platform Admin or Security Admin   |
| **Can it change levels**      | Can be promoted to Tenant by a Platform Admin or Security Admin | Cannot be demoted back to Personal |

## When to use a Personal Gateway

A Personal Gateway belongs to the user who created it. Only the creator can see it in the Gateway List, connect to it, or edit its configuration. Other users browsing the full Gateway List won't see a Personal Gateway that isn't theirs.

Use a Personal Gateway when you want:

* To test a new server before rolling it out more broadly
* A toolset tailored to your own workflow
* A private Gateway that other users don't need to see

## When to use a Tenant Gateway

A Tenant Gateway is shared across your entire organization. Every user in the tenant can see it and connect to it as an MCP endpoint. Only a Platform Admin or Security Admin can create, edit, or delete it; everyone else has read and use access but can't change its configuration.

Use a Tenant Gateway when you want:

* A shared, standardized toolset for a team, such as a support team's tools
* A company-wide set of approved integrations
* One Gateway that admins maintain and the whole organization consumes

## Promote a Personal Gateway to Tenant

If a Personal Gateway turns out to be useful for a wider group, a Platform Admin or Security Admin can promote it to Tenant visibility, making it available to everyone in the organization.

<Warning>
  Promoting a Gateway to Tenant is permanent. Once a Gateway is Tenant level, it can't be demoted back to Personal. To keep a private version alongside the shared one, create a separate Personal Gateway rather than converting your only copy.
</Warning>

## Naming rules

Gateway names must be unique across your entire tenant, not just among your own Gateways. If another user has already named their Personal Gateway "Support Tools," you can't reuse that name for a Gateway of your own. If you hit a naming conflict while creating a Gateway, pick a more specific name.

## What's the same either way

Visibility level changes who can see and edit a Gateway. It does not change how the Gateway behaves once connected.

**Connected app credentials.** The apps you connect to a Gateway (Slack, Jira, Google Drive, and so on) carry their own Personal or Tenant designation, separate from the Gateway's visibility setting. A Tenant Gateway doesn't require every connected app to be Tenant level, and a Personal Gateway can still use a Tenant-shared connection. See [Tenant vs. Personal Level App Credentials](/mcps/admin-controls/tenant-vs-personal-app-credentials) for how that works.

**Monitoring and activity.** Gateway visibility controls access to the Gateway's configuration, not who can see its usage. Whether a Gateway is Personal or Tenant, its activity is still included in tenant-wide monitoring for admins with that visibility. See [MCP Monitoring](/mcps/admin-controls/mcp-monitoring) for who can see what.

**Radar and Tool Scanning.** [Radar](/mcps/admin-controls/radar) and [Tool Scanning](/mcps/admin-controls/tool-scanning) work the same on both Personal and Tenant Gateways. Neither depends on the visibility level, so you can enable them on either type.

## Related Resources

<CardGroup cols={2}>
  <Card title="Tenant vs. Personal App Credentials" icon="key" href="/mcps/admin-controls/tenant-vs-personal-app-credentials">
    Set the visibility of each connected app's credentials
  </Card>

  <Card title="Editing a Gateway" icon="pen-to-square" href="/mcps/admin-controls/editing-a-gateway">
    Change a Gateway's apps, tools, and configuration
  </Card>

  <Card title="MCP Monitoring" icon="chart-line" href="/mcps/admin-controls/mcp-monitoring">
    See who can view a Gateway's tool calls and activity
  </Card>

  <Card title="Deployments vs. Gateways" icon="shuffle" href="/mcps/admin-controls/deployments-vs-gateways">
    Decide which connection model fits your use case
  </Card>
</CardGroup>