Members & Roles
Manage members, roles, teams, and project access in BrowserStack AI Evals.
Members & Roles
BrowserStack AI Evals uses a role-based access model layered on your BrowserStack identity. Two questions decide what any member experiences:
- What can they do? — set by their role (
Owner,Admin,Member). - What can they see? — set by their role combined with their team (sub-group) membership.
Identity & access
Identity is owned by BrowserStack — there is no separate evals sign-up:
- Members sign in with their BrowserStack account. Users are provisioned through BrowserStack login; a person who has never signed in cannot be added.
- An organization maps to a BrowserStack group, and a team maps to a BrowserStack sub-group.
- Roles and team membership are managed in your BrowserStack account. Settings → Members ↗ redirects there.
- Organization details and your personal profile are also managed in your BrowserStack account — open the user menu and choose Organization Settings or Personal Settings.
- Inside evals you assign projects to teams and can set per-project role overrides (see below).
Because membership is managed in BrowserStack, adding people, changing their role, or moving them between teams happens in your BrowserStack account, not in the evals dashboard.
Teams (Enterprise)
Creating and managing Teams — including adding members and assigning Team Admins — is an Enterprise feature at BrowserStack. Basic user management is available on other plans, but the structured Teams functionality (granular access control, license allocation by team, and delegated administration) is part of the Enterprise offering.
Key Enterprise Teams capabilities:
- Team creation & management — organize users into teams that mirror your organizational structure.
- Team Admins — let specific users help manage their own teams without needing full Owner/Admin privileges over the entire organization.
- Multi-team membership — users can belong to multiple teams (typically active in one at a time for data-access purposes).
- Product access mapping — control which products (e.g., Automate, Live, Test Management) each team can access.
Teams are managed from the Manage Teams page in the BrowserStack User Management Dashboard.
Personas
A member's persona is their role combined with whether they belong to a team.
| Persona | Role + team |
|---|---|
| Owner | Owner, not in a team |
| Group Admin | Admin, not in a team |
| Team Admin | Admin, in one or more teams |
| Group Member | Member, not in a team |
| Team Member | Member, in one or more teams |
Role permissions
This answers the "what can they do?" question. Roles gate individual actions at two scopes: organization (org-wide resources) and project (a single project). A project role can override the organization role for that project; the special role NONE means "use the organization role only."
Organization permissions
| Permission | Owner | Admin | Member |
|---|---|---|---|
| Create projects | Yes | Yes | — |
| Transfer projects | Yes | Yes | — |
| Update org settings | Yes | Yes | — |
| Delete organization | Yes | — | — |
| Manage org members | Yes | Yes | — |
| View org members | Yes | Yes | Yes |
| Manage billing | Yes | — | — |
Project permissions
| Permission | Owner | Admin | Member |
|---|---|---|---|
| View project | Yes | Yes | Yes |
| Update project settings | Yes | Yes | — |
| Delete project | Yes | — | — |
| Manage project members | Yes | Yes | — |
| View project members | Yes | Yes | Yes |
| Create/delete API key pairs | Yes | Yes | — |
| View API keys | Yes | Yes | Yes |
| Create/delete write-only keys | Yes | Yes | — |
| Manage LLM connections | Yes | Yes | Yes (update only) |
| View LLM connections | Yes | Yes | Yes |
| Manage integrations | Yes | Yes | — |
| Create/edit traces | Yes | Yes | Yes |
| Delete traces | Yes | Yes | — |
| Create/edit scores | Yes | Yes | Yes |
| Manage score configs | Yes | Yes | Yes |
| Manage datasets | Yes | Yes | Yes |
| View datasets | Yes | Yes | Yes |
| Manage prompts | Yes | Yes | Yes |
| View prompts | Yes | Yes | Yes |
| Manage protected labels | Yes | Yes | — |
| Manage evaluators / eval jobs | Yes | Yes | Yes |
| View evaluators / eval jobs | Yes | Yes | Yes |
| Manage experiments | Yes | Yes | Yes |
| View experiments | Yes | Yes | Yes |
| Manage online evaluations | Yes | Yes | Yes |
| View online evaluations | Yes | Yes | Yes |
| Manage models | Yes | Yes | — |
| Manage annotation queues | Yes | Yes | Yes |
| View annotation queues | Yes | Yes | Yes |
| Batch exports (create) | Yes | Yes | Yes |
| View batch exports | Yes | Yes | Yes |
| View audit logs | Yes | Yes | — |
| Manage dashboards | Yes | Yes | Yes |
| View dashboards | Yes | Yes | Yes |
Project access
This answers the "what can they see?" question. Projects belong to an organization (the group) and are each assigned to at most one team. A project with no team is group-level. What a member sees follows from their persona:
| Persona | Can create projects | Project visibility |
|---|---|---|
| Owner | Yes and assign to any team | All group-level and all teams' projects |
| Group Admin | Yes and assign to any team | All group-level and all teams' projects |
| Team Admin | Yes and assign to a team they admin (with multiple teams, one is the default and can be changed) | Only projects of the team(s) they admin (any creator) — not group-level, not other teams |
| Group Member | No | Only group-level projects (projects not assigned to any team) |
| Team Member | No | Only their team's projects (any creator) — not group-level, not other teams |
Lifecycle rules
- If a Group Admin is added to a team, they become a Team Admin for that team and lose group-wide visibility (they then see only their team(s)).
- An Owner is not part of a team, but still sees all group-level and all teams' projects.
- If a team is deleted, its projects are reassigned to the group level.
- A project is assigned to exactly one team, or to none (group-level).
Managing access
Adding members
Members are added in your BrowserStack account:
- Go to Settings → Members ↗ (opens BrowserStack account management).
- Add the user and select their role.
- Assign them to a team (sub-group) if they should have team-scoped access.
The person must have signed in with BrowserStack at least once to be added.
Managing team membership
Team membership is managed in your BrowserStack account:
- Only a Group Admin can add members to a team.
- A Team Admin can remove members from a team they administer.
Assigning projects to teams
A project's team is set when you create it, and can be changed afterwards from the project's Settings → General section. Who can assign to which team follows the project-access rules above.
Assigning project roles
Beyond visibility, you can override a member's role for a specific project:
- Go to the project's Settings → Members ↗.
- Find the member in the list.
- Select their project role from the dropdown.
- Changes take effect immediately.
Setting a project role to NONE means the member's access is determined solely by their organization role.