Manage data access for Test Management

Control visibility of data across multiple teams through advanced data access management

For privacy and security reasons, organizations often require team-based isolation of data. BrowserStack’s Manage Data Access feature enables you to isolate data access based on teams.

How does Manage Data Access work?

In BrowserStack, user accounts have different Identity and Access Management (IAM) roles assigned to them. A user can have one of the following roles: Org Owner, Org Admin, Org User, Team Admin and Team User.

To learn more about different IAM roles, see Manage Member Roles.

Data access settings

See the table below to understand what access Org and Team roles have when the Org Owner enables Team Access:

What data is available with Team Access?

To understand what data is available to you when Team Access is enabled, go through the following scenarios:

A user changes teams

If you move from one team to another:

• You can no longer access data of your previous team, even if you owned the data.
• You cannot create builds for projects associated with your previous team.
• You can create builds for projects associated with the new team.

A user moves from Org to Team

If you move from an Org role (Owner, Admin, or User) to a Team role (Admin or User):

• You can access data exclusive to the team.
• You cannot access data that you created in an Org role.
• You cannot create builds for projects associated with the Org role.
• You can create builds for projects associated with the new team.

A user moves from Team to Org

If you move from a Team role to an Org role, you can access all data in the organization, including the data you could access in the Team role.

• You can access all data in the organization, including the data you could access in the Team role.
• You can create builds for all projects.

Related topics

• Manage Data Access
• Manage Member Roles