Teams

A team is a named group of tools and members managed together. Instead of assigning each person to each tool individually, you set their role at the team level - and they immediately gain that role on every tool in the team.

Why teams exist

Without teams, access management gets repetitive as your organization grows. With ten tools and a group of contractors who need access to all of them, that’s ten assignments per person. Teams collapse that into one step.

Teams are also useful when your organization has distinct working groups - say a data team and a product team, each with their own tools and members. Teams let you model that structure cleanly.

Where to manage teams

Teams live at Settings → Teams (/user/teams). Only Owners and Admins can create or modify teams.

What a team contains

A team has two pieces:

A set of tools
A set of members, each assigned a team role (Editor, Executor, or Viewer)

The team role a member is assigned applies to every tool in the team. See Roles & Permissions for what each tool role can do.

Creating a team

Go to /user/teams and click Create Team.
Give it a descriptive name - “Data Tools” or “Client A” works better than “Team 1”.
Add the tools that team members should have access to.
Add the members and set each one’s role (Editor, Executor, or Viewer).

Role inheritance

Team roles flow from the team down to its tools:

Adding a member to a team grants them their team role on every tool currently in the team.
Adding a tool to a team grants every current team member their team role on that tool.
If the team grows later (new tools, new members), inheritance applies automatically - no extra assignments needed.

A member must already belong to your organization before they can be added to a team. If they’re not in the organization yet, send an invitation first from Inviting Members.

Changing team membership

Owners and Admins can add or remove members and tools from a team at any time.

Removing a member from a team revokes their access to every tool in the team, unless they have a separate direct assignment on a tool.
Removing a tool from a team revokes access for every team member who didn’t have a direct assignment on that tool.

Direct tool assignments and team-based assignments stack - a member keeps any access they were granted directly, even if their team membership changes.