User Groups and Permissions
User Groups let administrators manage access to Functional APIs and MCP tools at group level instead of per user. This page is for Hub administrators who create groups, assign users and grant API permissions.
Overview
A User Group is a collection of permissions and a security role that you assign to one or more Hub users. User Groups work with:
- Basic authentication
- OAuth authentication providers (such as Microsoft Entra ID / Azure AD)
- MCP server tool filtering and authorization
With User Groups you can:
- Organize users into logical groups.
- Grant access to specific Program Calls.
- Grant access to specific RPA definitions.
- Assign the User or Admin role.
- Control which APIs appear in discovery endpoints.
- Control which MCP tools are available to AI agents.
Concepts
User
A Hub user is authenticated through Basic authentication. A user can belong to multiple User Groups.
User Group
A User Group is a logical collection of permissions and a security role. Each group has:
- Group name
- Role (Admin or not)
- Program Call permissions
- Data API permissions
- RPA permissions
- Assigned users
Permission levels
Two permission levels are supported.
Regular functional access (not Admin)
Members can:
- Execute permitted Functional APIs.
- View permitted definitions.
- Use permitted MCP tools.
Members cannot access Admin APIs.
Built-in user group
The Hub creates a built-in non-admin group named user together with the default functional user. Members of the user group (and users with the user role provided by an OAuth provider) can execute all Program Calls, Data APIs and RPA Calls without any per-API permission.
Permissions assigned to a group apply to the groups that you create. A user who belongs only to such custom groups can execute only the APIs that these groups are permitted to use.
Admin
Administrative access. Members inherit administrative privileges. They can access Admin APIs, view and execute all Functional APIs (Program Calls, RPA Calls and Data APIs), and use all MCP tools.
Creating a User Group
Create a new group:
Example request body:
Setting the group role
After you create a group, assign its role.
To set the group as User, which is the recommended role for application users:
To set the group as Admin, which gives its members administrative privileges:
Creating users
Create a new Hub user:
Example request body:
Assigning users to groups
Add a user to a group:
A user can belong to multiple groups.
To remove a user from a group:
Managing Program Call and Data API permissions
Grant access to a Program Call or Data API definition:
Remove the permission:
Users who belong to a custom group can execute the corresponding Program Call API or Data API only if one of their groups has this permission. Administrators and members of the built-in user group can execute all APIs.
Managing RPA permissions
Grant access to an RPA definition:
Remove the permission:
Only authorized users can execute the corresponding Screen Automation endpoint.
Viewing group information
Retrieve group information:
Retrieve the assigned permissions:
List all groups:
Viewing user information
Retrieve user information:
List all users:
Allowed definitions
The Hub provides an endpoint that returns only the definitions available to the authenticated user:
Depending on the assigned User Groups, the response can contain:
- Program Calls
- Data APIs
- RPA definitions
Example response:
Administrators receive all registered definitions.
Permission enforcement
User Groups are enforced automatically during Functional API execution. If a user executes an API without the required permission, the Hub rejects the request. Administrators and members of the built-in user group are not restricted by API permissions.
Example response:
Admin APIs remain inaccessible unless the user belongs to an Admin group.
MCP integration
When MCP is enabled, User Groups also apply to the dynamically generated MCP tools. During authentication, MCP retrieves the allowed definitions of the user from the Hub and provides only the permitted tools.
For example:
| Permission | Visible MCP tool |
|---|---|
| Program Call | POSTORDSPQUERY_HUB |
| RPA | orderStatusURI_RPA |
Users cannot invoke tools that are not assigned to one of their groups. If a tool is unavailable, MCP returns an authorization error.
OAuth integration
User Groups can be mapped directly from OAuth provider roles. For Microsoft Entra ID (Azure AD), configure the Hub as follows:
auth.type=oauth
spring.oauth.resource.server.issuer-uri=https://...
spring.oauth.resource.server.authority.claim=roles
The value in the JWT roles claim must exactly match the name of the Hub User Group.
Example JWT payload:
A user who receives this token inherits the permissions of the sales-users User Group. For the full provider setup, see OAuth Configuration Guide.
Recommended workflow
- Create a User Group.
- Set the group role.
- Create users.
- Assign users to the group.
- Grant Program Call permissions.
- Grant Data API permissions.
- Grant RPA permissions.
-
Verify the accessible definitions:
-
Execute the Functional APIs.
- Verify MCP tool visibility (if MCP is enabled).
Best practices
- Manage permissions through User Groups instead of individual users.
- Create separate groups for different business functions.
- Grant only the minimum required permissions.
- Reserve Admin groups for administrative users.
- Use OAuth group mapping in production environments to avoid manual user administration.