> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.fabricgateway.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.fabricgateway.ai/_mcp/server.

# Manage namespaces

> Give each team its own space for routes, connections, credentials, analytics, traces, and people within one organization, and track what each team spends.

A namespace is a team's own space inside your organization. Without namespaces, every connection, route, credential, analytics chart, and trace appears together, and anyone who can change one team's routes can change every team's routes. With namespaces, each team manages only its own resources, and you can see what each team spends. This topic shows you how to create a namespace, add people to it, switch between namespaces, review all of them, and delete one.

## Prerequisites

Before you begin, make sure you have the following:

* Access to a Fabric AI Gateway organization.
* Permission to create and update namespaces, which the **Super admin** role has. You need it to see **Namespaces** under **Admin**.

## Understand namespaces

Each namespace isolates the following:

* Routes and connections, including LLM providers and MCP servers
* Credentials
* Analytics and traces
* People and their roles

Each namespace has its own roles, and a user can have a different role in each namespace. For what a **Namespace admin** and a **Member** can do, see [Understand roles and access](/configure/organization#understand-roles-and-access).

The people in a namespace can reach only that namespace's resources. This lets you limit who can change the configuration of production traffic, because a configuration change on the gateway can break production traffic.

Every organization has a namespace named **Default**. Resources that existed before you used namespaces are in Default, and nothing about them changed. You can't delete Default.

A caller's gateway key decides which namespace serves its requests. A key works only in the namespace that issued it, and a request with no key goes to the Default namespace. Namespaces have no URL form on the data plane, so a route's path doesn't name its namespace. For the full rules and the status codes that callers get, see [Understand how your key picks a namespace](/use/authenticate#understand-how-your-key-picks-a-namespace).

## Add a namespace

To add a namespace, do the following:

1. In the sidebar, select **Admin**, and then select **Namespaces**.
2. Select **Create namespace**.
3. Enter a **Name**. It must be unique in your organization, and you can change it later. Optionally, enter a **Description**, such as what the team owns.
4. Select **Create namespace**.

The console opens the new namespace. It starts empty, with no connections, routes, or traces. You can also select **Create namespace** at the bottom of the namespace switcher. In that case, the console makes the new namespace the active one.

## Add people to a namespace

People must already be members of your organization. To invite them first, see [Manage users and invitations](/configure/organization/users). To add them to a namespace, do the following:

1. In the sidebar, select **Admin**, select **Namespaces**, and then select the namespace.
2. On the **Overview** tab, select **Add members**.
3. Search for a person, and then select them.

The person joins as a **Member**. To make someone a **Namespace admin**, change their role in the list of members. You can also manage the people in the namespace that you're working in by selecting **Members** in the sidebar.

To change a role or remove someone, find them in the list of members, and then do one of the following:

* To change a role, use the role menu in their row, and select **Namespace admin** or **Member**.
* To remove someone, select the trash icon, and then select **Remove member**. They lose access to the namespace within a few seconds. Nothing is deleted, and you can add them back.

You need to be a Namespace admin of the namespace to add people, change roles, or remove people.

## Switch namespaces

To work in a different namespace, do the following:

1. At the top of the sidebar, select the namespace name.
2. In the **Switch namespace** menu, select a namespace.

The pages in the sidebar show only the resources in the namespace you selected.

## Review all namespaces

A **Super admin** can see every namespace in the organization. To review them, select **Admin**, and then select **Namespaces**. The list shows each namespace's name, with a **Default** badge on the default one, its description, and your role in it. To open a namespace, select it.

## Delete a namespace

You can delete any namespace except Default. Fabric doesn't check whether the namespace still holds resources, such as routes, so remove or move anything that you still need first. To delete a namespace, do the following:

1. In the sidebar, select **Admin**, select **Namespaces**, and then select the namespace.
2. On the **Overview** tab, select **Delete**.
3. Type the namespace's name to confirm, and then select **Delete namespace**.

You can't undo this. The namespace is removed with the upstream tokens stored under it, and its name becomes available again.

## Next steps

* To invite people to the organization first, see [Manage users and invitations](/configure/organization/users).
* To compare organization and namespace roles, see [Understand roles and access](/configure/organization#understand-roles-and-access).
* To cap what a team spends, see [Control spend with budgets](/configure/access-and-limits/budgets).