Skip to content
Reeflow
Start Building

Teams

Teams group platform users who share the same access requirements. You assign roles to teams rather than individual users, and all team members inherit those permissions.

Understanding how teams work requires familiarity with two components:

  • Members: Platform users who belong to the team. A user can belong to multiple teams.
  • Roles: Roles assigned to the team. All members inherit permissions from these roles.

When a platform user makes a request, Reeflow resolves their permissions through their team memberships:

  1. Identify teams: Find all teams the user belongs to.
  2. Check admin status: If the user belongs to the admin team, grant full admin permissions. Skip remaining steps.
  3. Collect roles: Gather all roles assigned to all of the user’s teams.
  4. Resolve permissions: Follow the standard role resolution process: filter assumable roles, merge permissions, and resolve user attributes.

Because permissions merge using union semantics, a user with multiple team memberships accumulates access from all teams. Adding a user to more teams never reduces their access.

A user belongs to two teams:

  • Engineering team: Has a role granting retrieve and update on connections
  • Analytics team: Has a role granting query on connections with table-level restrictions

The user’s effective permissions include both: they can view and modify connection settings (from Engineering) and run queries against allowed tables (from Analytics).

Every organization has a single admin team called Admin, created automatically when you create the organization. Members of the admin team have full permissions to all resources: Reeflow skips role resolution entirely and grants access to every action on every resource.

Use the admin team for:

  • Organization administrators who need unrestricted access
  • Initial setup before you configure granular roles

The admin team is system-managed. You can add or remove members (but at least one member must remain), and you cannot delete the team, change its name, or remove its admin status.

Team members inherit permissions from the roles assigned to their teams. When a user belongs to multiple teams, their effective permissions are the union of all inherited permissions. The permission merging rules apply: if any team grants an action, the user can perform it.

When roles assigned to teams have fixed user attributes, those values apply to all team members during role resolution. This lets you set organization-wide defaults through team role assignments.

Create a team in the Console

Create a new team to group users and assign shared permissions. This guide shows how to create a team and assign roles to it.

Navigate to Teams in the main navigation, then click New Team to open the form.

Enter a Name for the team. Choose a descriptive name that indicates the team’s purpose.

Optionally add a Description to explain who should be added to this team.

Expand Members and click Add Member to add users. Users inherit the team’s permissions immediately.

Expand Roles and select the roles this team should have. All team members inherit permissions from these roles.

Click Create Team to save. The team now appears in the list and members have access.

Reeflow enforces the following constraints on teams:

ConstraintLimit
Name length255 characters
Description length1000 characters

A team can have any number of members and roles. Users can belong to any number of teams.

ScenarioResult
User belongs to no teamsNo permissions granted; most requests return 403 Forbidden
Attempt to remove all members from the admin team403 Forbidden
Attempt to delete the admin team400 Bad Request
Attempt to rename the admin team400 Bad Request