You are setting up the Agent Hub and you are not sure which permissions your users need? This page describes standard setups for the common tasks.
You give a user one group per platform in the Users view of the Control Hub. The administrator of the platform or a user with Super Administrator permission assigns the group. Refer to Managing a User for details.
Groups
A user needs a separate group for each individual platform (e.g. dev, test, qa, prod etc.). A group determines what the user is allowed to do on that platform. The following groups are available:
|
Group |
Scope |
Description |
|---|---|---|
|
No access |
One platform |
Cannot access this platform, but can log in and inspect his user profile. |
|
Member |
One platform |
Can use what is deployed on this platform. Cannot make any changes to the platform. |
|
Developer |
One platform |
Builds, deploys and configures what runs on this platform. Cannot decide who else is granted access. |
|
Administrator |
One platform |
All developer rights. Can also decide who else should be granted access and which group that person should belong to. |
|
Super Administrator |
All platforms |
Can create, deactivate, and delete users on all platforms. This group does not grant access to the processes running on a platform. A super administrator can only assign groups. However, they may do so for any user, including themselves, on any platform. |
Member
Using What Is Deployed
Use Case: Your user should be able to use what is deployed on a platform, without changing it.
|
Group or Role |
Where to Assign |
Related Documentation |
|---|---|---|
|
Member |
Users view, on each platform the user works with |
Developer
Building, Deploying, and Configuring
Use Case: Your user should be able to deploy projects to a platform, and to update, configure, start, and stop the deployments.
|
Group or Role |
Where to Assign |
Related Documentation |
|---|---|---|
|
Developer |
Users view, on each platform the user deploys to |
Changing the Model Access of an Agent
Use Case: Your user should be able to assign a virtual API Key and a model to a deployed agent.
|
Group or Role |
Where to Assign |
Related Documentation |
|---|---|---|
|
Developer or Administrator |
Users view, on the platform the agent runs on |
Working With AI Coding Assistants
Use Case: Your user should be able to use the tools of the platform in an AI coding assistant.
These tasks need roles in the identity provider in addition to the group. Refer to Granting Access to the Platform MCP Server for details.
Administrator
Granting Access to a Platform
Use Case: Your user should be able to decide who gets access to a platform, and which group each user has on it.
|
Group or Role |
Where to Assign |
Related Documentation |
|---|---|---|
|
Administrator |
Users view, on the platform the user administers |
Configuring the Agent Gateway
Use Case: Your user should be able to manage the LLM providers and the virtual API Keys of a platform.
|
Group or Role |
Where to Assign |
Related Documentation |
|---|---|---|
|
Administrator |
Users view, on each platform whose Agent Gateway the user configures |
A user with the Developer role does not see the Agent Gateway pages.
Super Administrator
Managing Users on All Platforms
Use Case: Your user should be able to create, deactivate, and delete users, and to assign groups on every platform.
|
Group or Role |
Where to Assign |
Related Documentation |
|---|---|---|
|
Super Administrator |
Users view, section Global |
Section Global is only displayed to super administrators. It shows the groups that apply to all platforms. Currently, this is only the group Super Administrator.
A Super Administrator can use this section to grant another user super administrator rights. Enable the checkbox to give the group Super Administrator to this user.
The group Super Administrator does not grant access to what runs on a platform. To work on a platform, for example to configure its Agent Gateway, a super administrator also needs a group on that platform.
The last Super Administrator cannot be deactivated or deleted.