Play uses role-based access control (RBAC) at two different layers.
A workspace role answers, "Can this person manage the workspace itself?" A team role answers, "What can this person do inside this specific team?" Those two layers work together, but they do different jobs.
The simplest mental model is this:
-
Workspace roles control workspace-wide administration.
-
Team roles control day-to-day access to assets and configuration inside a team.
In shared workspaces, most practical product access comes from the team role, not the workspace role.
How the two layers fit together
-
A workspace role controls access to workspace settings and workspace user management.
-
A team role controls access to team assets and team-level configuration.
-
A workspace role by itself does not grant asset access. The user also needs access to one or more teams.
-
The same person can have different team roles in different teams inside the same workspace.
When you invite someone through the workspace-level user flow, you normally choose both:
-
A workspace role
-
One or more team assignments, each with its own team role
Workspace owners and workspace admins manage access across the whole workspace. Team administrators manage access only inside the specific team where they are an admin.
Workspace roles
These are the built-in workspace roles:
|
Workspace role |
What it means |
|---|---|
|
Owner |
Full workspace control. Can read and edit workspace settings and manage workspace users. A workspace can have only one owner. |
|
Workspace admin |
Can read and edit workspace settings and manage workspace users, including assigning people to teams and choosing their team roles. |
|
Member |
No workspace-settings access. Can still collaborate inside any teams they have been assigned to. |
Important details:
-
The regular workspace user-management flow does not let you change or remove the current workspace owner.
-
The regular workspace user-management flow does not let you edit your own workspace membership.
-
In practice, the workspace owner is the top-level admin for that workspace, and workspace admins help manage access without becoming the owner.
Team roles
These are the built-in team roles:
|
Team role |
Permissions |
What it means |
|---|---|---|
|
Administrator |
|
Can view and edit team assets and manage team members. |
|
Write |
|
Can view and edit team assets, but cannot manage team members. |
|
Read |
|
Can view team assets, but cannot edit them or manage team members. |
A team role applies only to that team. Someone can be an Administrator in one team and Read in another.
What each layer actually controls
|
Task |
Controlled by |
|---|---|
|
Open Workspace settings |
Workspace role |
|
Edit Workspace settings |
Workspace role |
|
Open the Users tab in workspace settings |
Workspace role |
|
Invite, update, or remove workspace users |
Workspace role |
|
Open a test case, runlist, file, knowledge base, or other team asset |
Team role |
|
Edit team assets |
Team role |
|
Edit team settings, environments, categories, statuses, tags, and secrets |
Team role |
|
Invite, change, or remove members in a single team |
Team role |
That means a person can be a plain workspace member and still do substantial work, as long as they have the right team role in the teams they belong to.
Guardrails and safety rules
Play prevents a few changes that would leave access in a broken state:
-
A workspace invite requires at least one team assignment.
-
A workspace can have only one owner.
-
The last team administrator cannot be removed or demoted.
-
The last member cannot be removed from a team.
-
Leaving a team is blocked if it would leave the team without another active administrator.
These guardrails are there to stop teams from accidentally locking themselves out.
Where to manage access in the UI
-
Workspace roles and workspace membership: Open the account menu, then go to Workspace settings -> Users
-
Team roles and team membership: Open the team from the Explorer, then use the team members area on the team page
-
Workspace settings: Open the account menu, then go to Workspace settings
-
Team settings and secrets: Open the team page in the Explorer
Personal vs. shared workspaces
In a personal workspace, the RBAC model is mostly invisible because you are effectively the workspace owner and the default member of your personal team.
In a shared workspace, RBAC becomes the main collaboration model. The workspace role decides who can administer the workspace. The team role decides where someone can actually work.