Settings

Every improvement tells a story. The table below highlights the key updates made to enhance the clarity, accuracy, and overall experience of this article.

S. No.	Updated Description	Updated On
2.	New User Role Access to upload the Role Template	7th August 2026
1.	Legacy Settings	4th May 2026

New User Role Access to upload the Role Template

The existing user roles (Admin, Analyst, and Operator) are replaced with new collaborator roles (Environment Admin, Manager, and Member).

This change introduces a more structured permission model, allowing organizations to assign access based on users' responsibilities while improving security and governance. It provides a stronger foundation for enterprise access management by introducing a more intuitive and scalable permission model.

Organizations can assign the right level of access to the right users, reducing administrative overhead while maintaining operational efficiency.

Existing User Role Mapping

Existing users will continue with their current role mappings and will not be migrated to the new collaborator role template.
The updated role mapping is applied only to newly created users, ensuring a smooth transition without impacting existing user access.

Role Permissions

The following table describes the role permissions:

Role	Access
Environment Admin	Full edit access across all modules in the Apex screen, including Logs.
Manager	Full edit access across all modules in the Apex screen, except Logs.
Member	View-only access to Projects and full access across all other modules, except Logs.

The following infographic depicts the summary of above enhancement at a glance:

Example

Consider an organization onboarding a new integration team:

The Platform Administrator is assigned the Environment Admin role to manage environments, collaborators, and all platform configurations.

The Integration Lead is assigned the Manager role to create, manage, and deploy integrations without access to Logs.

A Support Engineer is assigned the Member role, allowing them to monitor and work with integrations while having view-only access to Projects and no access to Logs.

This role-based approach ensures every user has the appropriate level of access, improving both productivity and security without compromising governance.

The following screenshot displays the updated roles available within the application.

Updated Screenshot

Figure: User Role Mapping

Legacy Settings

The Configuration/Settings page is where an administrator can manage core aspects of the Integration Hub access. Through this page you can configure how the Hub behaves globally — manage user access, configure the environment where the integrations must work, handle security/data settings, by defining the Workspace IDs.

To configure the Settings of the Integration Hub, perform the following steps:

Log in to the Application as an Admin.
Navigate to Integration Hub > User > Settings.
To configure user and assign a role template for a particular environment such as staging, prod.
Figure: Integration Hub Navigation
Enter the Details in the required fields.
For more information, refer to the Field Description.

Figure: Settings

Field Description

Field	Description
Details
Environment Type	Select the Environment Type from the dropdown. The list contains the following options: Dev: The environment used to design integrations. Test: The controlled environment used to test integration workflows before they go live. Prod: The live environment where integrations are actively used.
Workspace ID	Enter Workspace ID, this is an identifier that distinguishes between different workspaces or tenant instances within the Integration Hub.
Dev Workspace ID	Enter Dev Workspace ID, this is an unique identifier that represents a specific development workspace within the platform.

Enter the Details in the User Role Mapping fields.
For more information, refer to User Role Mapping Field Description.

Figure: User Role Mapping
Note
User Role Mapping in an Integration Hub defines how individuals or user groups are assigned specific roles, access levels, and permissions for the hub’s functionalities and integrations.

User Role Mapping Field Description

Field	Description
User	Select the user for mapping to roles in the Integration Hub Settings.
Role	Assign a role to the user based on the permissions. The dropdown contains the following options: Admin Analyst Operator Note Analyst cannot access Logs under the Tools of Integration Hub. Operator cannot access Tools that include Logs, Lookup Tables, Message Templates.

Field

Description

User

Select the user for mapping to roles in the Integration Hub Settings.

Role

Assign a role to the user based on the permissions. The dropdown contains the following options:

Admin
Analyst
Operator

Note
Analyst cannot access Logs under the Tools of Integration Hub.
Operator cannot access Tools that include Logs, Lookup Tables, Message Templates.

Click Add to insert the values in the user list.
Note
The User details in an Integration Hub identifies the roles or users authorized to access specific platform features, data, or settings. By assigning permissions based on user roles or specific requirements, it helps manage the environment and enhance security.
The user added is displayed in the list.
For more information, refer to the List Description.

Figure: User List

List Description

Column Name	Description
User Name	Identify the user using the username.
E-mail ID	This column displays the email ID of the user.
Role	View the Role assigned to the user by the admin.
Action	Perform actions such as Edit or Delete by clicking on the respective icon as described below: Click on the edit icon to edit the user details. Click on the delete icon to remove the user from the list.