Organization settings give administrators a central place to manage the identity and feature configuration of their Gatling Enterprise Edition organization. From here you can update your organization’s display name and slug, and control which platform capabilities are available to your users—enforcing, for example, the exclusive use of private packages and locations in environments where all test traffic must stay within your network.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 organization settings
Click the Organization settings button in the top navigation bar, or select Organization from the main menu. Both routes lead to the same settings page.Profile settings
The profile panel displays and allows editing of your organization’s core identity:| Field | Description |
|---|---|
| Avatar | Auto-generated from the first two characters of the Organization Name. Not customizable. |
| Organization Name | The display name shown throughout the UI. Click the pen icon to edit. |
| Organization Slug | A unique lowercase string with dashes (-) used in URLs and integrations. The slug is used in SSO redirect URIs and other integration endpoints. |
Feature management
The feature management section is visible only to organizations that use private locations. Each toggle controls the availability of a platform capability for all users in the organization.Feature toggles require Administrator access and are visible only to organizations with private locations activated.
Managed packages
Default: Enabled Controls whether users can create, upload, and use managed packages (packages stored on Gatling’s infrastructure). When disabled:- Users cannot create, upload, or update packages from the Sources view
- Users cannot create new tests that reference a managed package
- Users cannot launch existing tests configured with a managed package
- Previously created managed packages remain visible in the Sources view and can be deleted
Managed locations
Default: Enabled Controls whether users can deploy load tests to Gatling-managed cloud locations, including locations that use dedicated IPs. When disabled:- Users cannot create new tests with a managed or dedicated-IP location
- Users cannot launch existing tests that reference at least one managed or dedicated-IP location
No-code simulations
Default: Enabled Controls whether users can create and run no-code tests through the UI builder. When disabled:- Users cannot create new no-code tests
- Users cannot launch existing no-code tests
Public links
Default: Enabled Controls whether users can generate shareable links that allow non-authenticated access to run reports. When disabled:- Users cannot create new public links to run reports
- All existing public links are immediately invalidated
Custom build command
Default: Disabled Controls whether users can configure a custom build command when creating a simulation from a Git repository. When enabled:- Users can specify an arbitrary shell command to build the Gatling simulation from source instead of the default plugin-based build process