Namespaces

One organization,
every team in its own space.

Give each team its own namespace for connections, services, analytics and traces, and decide who can change what, without running a separate gateway per team.

One organization, separate namespacesPlatform teamPayments teamData teamNamespacesRoles per namespaceConnections & servicesPer namespaceAnalytics & tracesPer namespaceUsers & rolesPer namespace
Teams share one organization and one gateway, but each works only with its own namespace’s resources.
1
organization for every team
2
roles: Super admin and Member
0
extra gateways to run

The problem

Without isolation, every team in an organization sees every connection, service, chart and trace. A change meant for one team’s staging route can break another team’s production traffic, and the only way to separate them is to run more gateways, each with its own configuration to keep in sync.

Solution

A namespace groups a team’s connections, services, analytics, traces and users inside one Fabric organization. Switch namespaces from the top of the sidebar and every page shows only that namespace’s resources. People get a role per namespace, so the same engineer can be a Super admin in their team’s namespace and a Member in another. Resources that have not been assigned yet stay in the Default namespace.

What you get

Isolated resources

Connections and services belong to one namespace.

Scoped analytics and traces

Each team sees its own usage, cost and traces, not everyone’s.

Roles per namespace

Super admin or Member, set separately in each namespace.

Safer production changes

Limit who can change production configuration.

Default namespace

Existing resources keep working while you move them over.

Frequently asked questions

  • What does a namespace separate?

    A namespace holds one team’s connections and services, its analytics and traces, and its users and their roles, inside a single Fabric organization.

  • What roles can people have in a namespace?

    Super admin and Member. Roles are set per namespace, so the same person can be a Super admin in one namespace and a Member in another.

  • What happens to resources that already exist?

    Resources that are not assigned to a namespace stay in the Default namespace, so current traffic keeps working while you organize.

  • How do I create a namespace?

    Go to Admin > Namespaces and select Create namespace, or create one from the namespace switcher at the top of the sidebar. A new namespace starts empty.

  • Which plans include namespaces?

    Namespaces are available on both the Free and Enterprise plans.

Bring every AI interaction under control

Connect your first model, MCP server or internal API and apply consistent governance from one gateway.