Documentation Index
Fetch the complete documentation index at: https://docs.poolside.ai/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Roles define what users can do in Poolside. Poolside uses role-based access control (RBAC), where a role groups permissions that you assign to one or more teams. Users inherit permissions through their team memberships. You manage roles from Organization >How roles work
- Denied by default: Poolside denies permissions unless a role explicitly grants them.
- Team assignment: You assign roles to teams, not directly to users. Each team has exactly one role.
- Multiple teams: You can assign a role to multiple teams.
- Combined permissions: If a user belongs to multiple teams, Poolside combines the permissions from all assigned roles.
- Multiple resource types: A role can include permissions across different resource types, such as agents, repositories, and sandboxes.
System roles
System roles are built-in roles that Poolside creates and manages. In Organization >-
tenant-admin
Grants full administrative access, including creating and managing all resources, users, teams, roles, API keys, SCIM provisioning, and audit logs. -
developer
Serves as the default role when you create a team without selecting another role. This role does not include any permissions, so it does not grant access to agents, sessions, or other resources on its own. Users gain access only through team membership and the permissions in the roles assigned to those teams.
User-created roles
User-created roles are roles that you create and manage. In Organization >Permissions
Roles group permissions that grant actions on specific resource types. Poolside groups permissions by resource type, such as agents, repositories, MCP servers, and sandbox definitions. For a complete list of available permissions, see Permissions reference.Create a role
To create a role, you must provide a unique name and at least one permission. Prerequisites- You belong to a team with the
tenant-adminrole.
- In the Poolside Console, navigate to Organization >
Roles.
- Click New Role.
- Enter a Role Name.
- Optional: For Assign Teams, select one or more teams to assign this role to immediately.
- Add permissions to the role:
- Click Add Permission.
- For Scope, select whether this permission applies to Specific resources or to All existing and future resources of this type.
- Select a resource type, such as Agent, Repository, MCP Server, or Sandbox Definition.
- Select the allowed actions for that resource.
- To add additional permissions to the role, click Add Permission and repeat the previous step.
- Click Create Role.
Add or remove permissions from a role
You can add or remove permissions from roles in your organization. Prerequisites- You belong to a team with the
tenant-adminrole.
- In the Poolside Console, navigate to Organization >
Roles.
- Click the ellipsis (…) in the row for the role you want to edit and select Edit Role.
- Under Add Permissions, add or remove permissions as needed.
- Click Save.
Assign or remove teams for a role
You can assign or remove teams for roles in your organization. Prerequisites- You belong to a team with the
tenant-adminrole.
- In the Poolside Console, navigate to Organization >
Roles.
- Click the ellipsis (…) in the row for the role you want to edit and select Edit Role.
- Under Assign Teams, add or remove team assignments as needed.
- Click Save.
Delete a role
Deleting a role removes it from all assigned teams. Users who relied on that role lose the permissions granted by the role. Prerequisites- You belong to a team with the
tenant-adminrole.
- In the Poolside Console, navigate to Organization >
Roles.
- Click the ellipsis (…) in the row for the role you want to delete and select Delete Role.
- Review the confirmation dialog, which lists the teams currently assigned to the role.
- Click Delete to confirm.