Project access controls

Learn how to manage project access controls in BrowserStack.

Project access controls let you specify which users can access each project. These controls provide granular and flexible permission management for supported products, allowing you to go beyond traditional group-level access.

BrowserStack uses Unified Data Access Control (UDAC) to manage who can access project data. There are three main access levels:

• Global Access
• Project-Based Access Control (PBAC)
• Team Access

For more information on managing data access, refer to the Manage data access section.

Suppose your organization has the following projects:

• Project 1
• Project 2
• Project 3
• Project 4

Here’s how each access level works for projects:

Global Access

All users in the organization can view and collaborate on every project.

Example: If Global Access is enabled, all users can access Project 1, Project 2, Project 3, and Project 4 without restriction.

Project-Based Access Control (PBAC)

With Global Access, you can use Project-Based Access Control (PBAC) to set project-specific permissions. When you create a project, choose whether everyone in your organization can access it or restrict access to selected teams and users.

• Organization-wide projects: Accessible to all users in the organization. For example, create Project 1 and Project 2 org-wide to promote cross-team collaboration and shared ownership.
• Restricted projects: Accessible only to specific users or teams. For example, restrict Project 3 and Project 4 to the QA team and select developers working with client data.

For details on creating projects with specific access controls, see the create projects section.

Team Access

When you select Team Access, only the project creator and their assigned team can access the project. Other users and teams in the organization cannot view or contribute to the project, except for users with the Owner or Admin roles. If no team is assigned, the project is accessible to the group users.