Teams

A team is a named group of resources and members managed together. A resource can be a tool, an agent, or a workflow. Instead of granting each person access to each resource individually, you set their role once at the team level - and they immediately get that role on everything the team holds.

Why teams exist

Without teams, access management gets repetitive as your organization grows. With ten tools, three agents, and a couple of workflows that a group of contractors all need, that’s fifteen grants 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 support team, each with their own tools, agents, and workflows. Teams let you model that structure cleanly.

Where to manage teams

Teams live at Settings → Teams (/user/teams). Only Owners and Admins can create teams, rename them, and change what a team holds. Regular members can open the teams they belong to and see what those teams give them.

What a team contains

A team page has four tabs:

Tab	What it holds
Members	The people on the team, each with a team role (Executor or Editor)
Tools	Tools the team can reach
Agents	Agents the team can reach
Workflows	Workflows the team can reach

Two things are worth separating in your head:

• Enabling a resource for a team says only that the team may reach it. It grants no level of its own.
• A member’s team role says what that member may do with everything the team holds - run it, or run and change it.

So a team of Editors holding an agent can all rewrite it, while a team of Executors holding the same agent can only chat with it. See Roles & Permissions for the full breakdown per resource type.

Creating a team

1. Go to /user/teams and click Create Team.
2. Give it a descriptive name - “Data Tools” or “Client A” works better than “Team 1”.
3. On the Members tab, add people and set each one’s role. The Default access selector sets the role new members get when you add them; it starts at Executor so nobody arrives able to change things by accident.
4. On the Tools, Agents, and Workflows tabs, add the resources the team should have access to.

Adding tools, agents, and workflows

On each resource tab an Owner or Admin sees the whole organization’s catalogue of that kind - enabled rows and available rows in one list. Click + on a row to enable it for the team, or the remove icon to take it away. You can search by name and filter by visibility (Private, Organisation, or Public) to find what you’re after.

A resource must belong to your organization to be added to one of its teams. Adopted marketplace copies count, since the copy lives in your org.

Members of a team see only the resources their team already holds, with a link to open each one.

Team roles

Each member of a team has one of two roles:

Role	Can do
Executor	Run the team’s copy directly - run a tool, chat with an agent, run a workflow - without adopting it.
Editor	All of the above, and change it - a tool’s code, an agent’s instructions and setup, a workflow’s graph.

Change a member’s role at any time from the Members tab. The role applies to every tool, agent, and workflow in the team - there’s no per-resource override inside a team. If one person needs to edit a single agent but only run everything else, put that agent in its own team.

Role inheritance

Team roles flow from the team down to everything it holds:

• Adding a member to a team grants them their team role on every resource currently in the team.
• Adding a resource to a team grants every current member their team role on it.
• If the team grows later - new resources, new members - inheritance applies automatically. No extra assignments needed.
• If someone is on several teams that hold the same resource with different roles, the highest role wins.

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.

Who is always an Editor

Two kinds of people get Editor access without a team grant:

• Org Owners and Admins can change any tool, agent, or workflow in the organization.
• The creator of a resource can always change their own work, even if no team of theirs holds it.

Everyone else needs an Editor role on a team that holds the resource. A plain member who didn’t create an agent or workflow and isn’t on a team that holds it as Editor cannot change it, even though they can see it exists in the organization.

Agent seats

A team role and an agent seat are separate grants. On plans with a seat cap (Team and Enterprise), a member needs an agent seat to actually run agents, whatever their team role says. The Members tab shows a Seat or No seat tag on each row, and Owners and Admins can grant a seat right there - or buy one if every seat is in use. Free Personal and Pro have no seat cap, so the tag doesn’t appear. See Subscription for how seats are priced.

Changing team membership

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

• Removing a member from a team revokes their access to every resource in the team, unless they reach it another way - a direct assignment on a tool, another team, or being its creator.
• Removing a resource from a team revokes access for every team member who doesn’t reach it another way.

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