Team administration
How team admins work, what they can override, and how to structure your org into teams.
What a team is
A team is a group of users that can have its own settings and its own shared assistants. Teams are useful when different groups in your organization have different needs — the sales team might have different skills installed than the engineering team. Each team can be scoped independently without affecting the rest of the org.
Teams are created by org admins in Organization → People → Teams (type a name and click Create team), or provisioned automatically via SCIM group sync. Expanding a team in that list shows its members and their roles.
The inherit / on / off model
Team settings that come from the organization have three states:
| State | What it means |
|---|---|
| Inherit | Use whatever the org setting says. Changes to the org setting flow through automatically. |
| On | Explicitly enabled for this team — but only if the org allows it. |
| Off | Explicitly disabled for this team, regardless of org default. |
In the team settings, Inherit is the unselected state: pick On or Off to override, and click the active option again to go back to inheriting.
A team admin cannot set something to On if the org has it set to Off. The org setting is the ceiling.
For example: if org admins have turned off "Install from Store" for skills, a team admin cannot re-enable it for their team. But if the org has it On, a team admin can set it to Off for their team to restrict their users further.
What team admins can configure
Team admins manage their team from Team in the account menu (the page is titled Admin when you are the only member). Only team owners, team admins and org admins can open it. It has these tabs:
- People — the team's members (with their roles) and pending Invitations
- Assistants — shared assistants for the team
- Connections — which connections are enabled for the team, how much access each provider grants, custom connections, and the team's Microsoft Teams connection
- Skills & Workflows — skills installed for the team, blocking skills pushed from above, the skill store, and what members may browse, install, create and share
- Task Templates — task templates for the team
- Settings — team name, the shared context given to all team members' assistants, and invitation approval (below)
- Billing — only for teams that are not part of an organization
Team admins cannot change SSO configuration, audit log settings, domains, or the organization's billing — those stay with org admins.
Team roles
Every team member is an Owner, Admin or Member. Owners can assign any of the three roles; admins can assign Member or Admin. Nobody can change their own role, admins cannot remove other admins, and only an owner can remove an owner.
To change someone's role, go to Team → People → Members and use the role dropdown next to their name.
Inviting people
Team admins invite people by email under Team → People → Invitations, where they can also revoke pending invitations. If Require admin approval for invitations is on in Team → Settings, invitations requested by regular members wait for an owner or admin to approve or reject them. That setting applies to teams that are not part of an organization; for teams inside an organization, membership is managed by the organization.
Team-level assistants
Teams can have shared assistants, created in Team → Assistants. Team admins control which skills are available to the team through the Skills & Workflows tab.