Teams are the primary unit of resource isolation in Gatling Enterprise Edition. Packages, simulations, API tokens, and reports all belong to a specific team, and user permissions can be scoped per team so that contributors only see and act on resources relevant to them. Teams also serve as the unit for credit quota management—organization administrators can cap how many credits each team consumes per billing period, making it straightforward to allocate load-testing capacity across multiple groups or projects.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 teams page
Navigate to Organization in the navigation menu and click the Teams tab.The teams table shows only the teams you belong to. Administrators see all teams in the organization.
Creating, editing, or deleting teams requires Administrator access.
The teams table
For each team you can see:| Column | Description |
|---|---|
| Team name | The display name of the team |
| Members | The number of members. Click the link to see the member list. |
| Credits consumed | Credits used by this team in the current billing period |
| Quota | The configured credit quota limit (Administrator only). Click the edit icon to change it. |
| Linked resources | Pills showing associated API tokens, tests, packages, and repositories. Click any pill to see the linked items. |
Creating a team
Enter the team name
Provide a descriptive name that identifies the team’s purpose—for example,
Platform Engineering, QA Automation, or Frontend Performance.Save
Click Save. The new team appears in the table immediately. You can now assign users to it via the Users page and add resources (packages, simulations, tokens) with this team as the owner.
Managing teams
Using the kebab menu (⋮) at the end of each row, you can:- Copy team ID — useful for API calls and configuration-as-code references
- Edit team name — only available to Administrators
- Delete team — only available to Administrators (see warnings below)
Credit quotas
Usage quotas let you control credit consumption on a per-team basis. Once a team reaches its quota for the billing period, its members cannot start new test runs until the period resets or the quota is increased.You must be an Organization Administrator with an annual plan to set team credit quotas.
Setting a quota
Open the quota editor
In the Quota column of the teams table, click the edit icon (✏️) next to the team you want to configure.
Enter the quota value
Enter the maximum number of credits the team can consume per billing period. Leave the field empty to allow unlimited consumption.
Annual vs. monthly quota periods
You can switch a team’s quota period between annual and monthly from the quota settings. Be aware that switching resets the previously set quota value for that team.Team membership and roles
Users are assigned to teams via the Users page. Each user can have a different role in each team—for example, a user might be a Team Leader in thePlatform Engineering team but only a Team Viewer in the Marketing team.
For the full role hierarchy and permission details, see User Management.