User management in Gatling Enterprise Edition gives administrators fine-grained control over who can access which resources and perform which actions. Roles can be assigned at the organization level (applying globally) or at the team level (restricting scope to resources belonging to a specific team). This model lets you grant broad access to trusted team leads while keeping individual contributors isolated to their own team’s simulations and reports.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/gatling/gatling.io-doc/llms.txt
Use this file to discover all available pages before exploring further.
Accessing the users page
Navigate to Organization in the navigation menu and click the Users tab. You must have the Administrator role to view and manage all users. Users with lower roles see only their own profile.Understanding roles and permissions
Gatling Enterprise Edition has two tiers of roles: organization-level roles (apply to all teams) and team-level roles (apply only to the assigned team).Organization-level roles
| Role | Description |
|---|---|
| Administrator | Full access to all organization resources, billing, user management, and settings. |
| Leader | Manages packages, repositories, and tests for all teams. Cannot manage users or billing. |
| Tester | Creates and runs simulations for all teams. |
| Contributor | Can start runs and generate public links, but cannot create simulations. |
| Viewer | Read-only access to reports and trends for all teams. |
Team-level roles
Team-level roles follow the same hierarchy as organization-level roles, but permissions apply only to the resources belonging to the assigned team.| Role | Description |
|---|---|
| Team Administrator | Full access to resources within the team. Can invite users to the team. |
| Team Leader | Manages packages, repositories, and tests within the team. |
| Team Tester | Creates and runs simulations within the team. |
| Team Contributor | Can start runs and generate public links for the team. |
| Team Viewer | Read-only access to the team’s reports and trends. |
Permission matrix
| Viewer | Contributor | Tester | Leader | Administrator | |
|---|---|---|---|---|---|
| Access own profile and Organization page | ✅ | ✅ | ✅ | ✅ | ✅ |
| Access Reports and Trends | Own team | Own team | Own team | Own team | Own team |
| Start Simulation | — | Own team | Own team | Own team | Own team |
| Generate Public Links | — | Own team | Own team | Own team | Own team |
| Create Simulation | — | — | Own team | Own team | Own team |
| Administrate Packages and Git Repositories | — | — | — | Own team | Own team |
| Administrate API Tokens, Users and Teams | — | — | — | — | Own team |
| Subscribe and view Offers | — | — | — | — | ✅ (org-wide only) |
For team-level roles, “Own team” means the user can perform the action only on resources belonging to the team(s) where they hold that role.
Inviting new users
Enter email addresses
Add one or more email addresses in the Email address field. Separate multiple addresses with a comma or a space to batch-invite users with the same permissions.
Assign roles
Select an organization-level role, and optionally assign one or more team-level roles. See the permissions matrix above for guidance on which role best fits each person’s responsibilities.
Viewing pending invitations
Click the Invitations tab on the Users page to see all outstanding invitations. From here, you can resend an invitation that has expired or was not received using the Resend invitation button.Editing or removing users
- Edit roles: click the Edit roles button next to any user in the table to modify their organization or team assignments.
- Remove a user: select the checkbox to the left of the user’s name, then click Delete at the top of the table. The user is removed from the organization and loses access to all resources.