Roles and permissions for Load Testing

Manage user access to BrowserStack Load Testing with centralized RBAC, covering IAM roles, RBAC roles, project access levels, and custom roles.

BrowserStack’s centralized Role-Based Access Control (RBAC) provides a single model for roles and permissions that covers all products, including Load Testing. Use IAM roles and RBAC roles together to control who can create, run, and manage load tests, and who can only view results.

Types of roles

BrowserStack uses two broad categories of roles to manage user access:

• IAM roles: Control the ownership and administrative privileges across all BrowserStack products.
  • Owner: Has complete control over organization settings, member management, and product access. Only one owner is permitted.
  • Admin: Has extensive administrative capabilities, including managing users and granting product access, but lacks ownership privileges.
  • User: Can use the products that they have access to, without administrative rights.
• RBAC roles: Define what a user can do within Load Testing. The RBAC roles are:
  • Admin: Full permissions to view, create, update, delete, and manage all Load Testing entities.
  • User: Moderate permissions tailored to running and managing load tests.
  • Viewer: Read-only access to load tests and reports.

Refer to Types of roles for detailed information about role types.

Member and guest roles

After assigning IAM and RBAC roles, set the user’s access level for Load Testing:

• Member (licensed): A fully licensed user with complete operational access aligned with their RBAC role.
• Guest (unlicensed): An unlicensed user with limited, view-only access.

Refer to Member and guest roles for each product for more information.

Permissions matrix

The following table summarizes what each RBAC role can do in Load Testing by default.

Project access levels

Load Testing projects have access levels that control who can view them. Roles control what a user can do; access levels control who can see the project:

• Private: visible only to the project’s members.
• Restricted: visible to a specific set of members.
• Organization-wide: visible to everyone in the organization who has access to Load Testing.

Project visibility is managed through Project Management, not by the Load Testing role. If you can’t see a project you expect, it may be Private or Restricted and not shared with you. Ask the project owner or your admin for access. Refer to Project access controls for more information.

Override access at project level

You can override a user’s default RBAC role within a specific Load Testing project by assigning a different role for that project. This gives someone broader or narrower access to one project without changing their access to other projects.

Refer Override access at a project level for steps to override a user’s role at the project level.

Custom roles

If the default Admin, User, and Viewer roles don’t meet your requirements, you can create custom roles with specific permissions for Load Testing. Custom roles let you:

• Grant specific permissions to meet unique workflows.
• Limit access to sensitive areas to authorized personnel only.
• Align access control with organizational policies or compliance requirements.

Refer to Manage custom roles to create or modify custom roles.

Assign roles

You can assign roles when inviting new users or modify roles for existing users. You can also request access if you need additional permissions.

Invite users

Refer to Invite users to invite users and assign their IAM role and RBAC role for Load Testing.

Modify roles

Refer to Modify access for a user to change a user’s IAM role, RBAC role, or product access for Load Testing.

Request access

If you need more permissions than your current role allows, you can request access from an Admin or Owner in your organization. Use the Request Access option in the Load Testing interface to notify them of your needs.

Project Management integration

Load Testing projects participate in BrowserStack’s centralized Project Management, so RBAC and project access levels stay consistent with other products linked to the same project.

Related topics

• Centralized Role-based access control (RBAC)
• RBAC roles and permissions
• Project access controls
• Manage custom roles