Permissions & Roles
Assign granular roles to control access to different servers
Introduction
You can give organization users, service accounts, and teams different levels of access to servers by assigning them to roles. Choose the role that best fits each member or team's function in your organization without giving people more access to the server than they need. For what those three principals are, and how a team grants a role to its members, see People & Teams.
From least access to most access, the roles for an organization's servers are:
- No Permissions: user cannot see or interact with the server
- Member: able to see and call the tools
- Maintainer: able to modify the server configuration
- Admin: modify permissions and delete the server
Organization owners can set base permissions that apply to all members of an organization when accessing any of the organization's servers. For more information, see How Access Is Decided and Set Base Permissions below.
How Access Is Decided
A member can reach a server for any one of four reasons. An empty member list on a server does not mean nobody can use it.
- A membership on the server. The member, or a team they belong to, is added to that server with a role.
- A profile. A profile that includes the server is assigned to the member or to one of their teams.
- The server's Visibility. A server set to Organization can be used, as Member, by everyone in the organization.
- The base role of the organization. If it is anything other than No Permissions, every member holds that role on every server, without being added to anything. See Set Base Permissions below.
A member gets the highest role that any of these reasons gives them. Organization owners have full permissions whatever the four say, with two exceptions. A session that applies a restrictive profile is narrowed to that profile, owner or not. And an organization can decide that its owners are offered tools over MCP the way members are; see Owners Over MCP below.
Visibility Is Not The Same As Access
A server's Visibility and the organization's base role are two independent ways in. Either one on its own is enough to let every member use a server:
| Base role | Visibility | Who can use the server |
|---|---|---|
| No Permissions | Private | Only the people and teams you added, plus profiles and owners |
| No Permissions | Organization | Every member, as Member |
| Member, Maintainer or Admin | Private | Every member, at the base role |
| Member, Maintainer or Admin | Organization | Every member, at the base role |
To restrict a server to named people only
Set the server's Visibility to Private and the organization's base role to No Permissions. Changing only one of the two leaves the server open to every member.
For narrowing what one client or agent may reach, use a restrictive profile instead.
Base Member Privileges
You can set base permissions that apply to all members of an organization when accessing any of the organization's servers.
To change it, go to Settings in the left sidebar and find Base Member Privileges. In the public API the field is memberDefaultRole on the organization.
A new organization starts at No Permissions. Members then reach a server only through a membership, a profile, or the server's Visibility. Raise the base role when you want everyone to have the same role everywhere without granting it server by server.
If someone with admin access to an organization's server grants a member or a team a higher level of access for the server, the higher level of access overrides the base permission. The base role never lowers a role somebody already has.
Members with the organization role of Owner always have full permissions, whatever the base role is.
Note that all changes to base permissions will affect both new and existing members.
Raising the base role opens every server at once
The base role applies to every server in the organization, including servers added later. Setting it to Admin, for example, lets any member change the configuration of, and delete, every server.
Organization Owners & MCP
Gatana will by default only send the tools to an organization owner if they are granted access to them as non-owner would. This is since an owner can see and manage everything in the organization, and they might use Gatana over MCP but not need everything (for example if they configured Gatana for several different teams).
This is configurable under Settings in the left sidebar, with Make all tools available to organization owners over MCP:
- Off (default): an owner over MCP is sent only the tools they have explicit grants to (like a non-owner)
- On: all the tools of every server in the organization are sent.
Credentials and Clients
You restrict a credential, client (e.g. OAuth client), or a team, by using a profile.
Server Creation Privileges
In a new organization by default all users are allowed to create servers. You can control this in the organizational settings.
Whoever creates a server becomes its Admin. They can configure it, decide who else reaches it, and delete it, without anybody granting them anything. This matters because a new server is Private and the base role is No Permissions, so without it the creator could not see their own server.
Last updated on