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 AI assistant configuration. Teams are useful when different groups in your organization have different needs — the sales team might have Salesforce connected, while the engineering team has GitHub. Each team can be scoped independently without affecting the rest of the org.
Teams are created by org admins in Organization → Teams, or provisioned automatically via SCIM group sync.
The inherit / on / off model
Every team setting has 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, regardless of org default — but only if the org allows it. |
| Off | Explicitly disabled for this team, regardless of org default. |
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 disabled "Install from store" (skills marketplace installs), 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 settings → Admin:
- Skills access — browse store, install from store, create custom skills (each can inherit/on/off within org limits)
- Connections — which external services team members can connect
- Sharing policy — whether team members can share tasks or contacts outside the team
- Members — add or remove team members, assign sub-admins
Team admins cannot change SSO configuration, audit log settings, or billing — those stay with org admins.
Assigning team admins
Any team member can be made a team admin. Go to Team settings → Admin → Members, find the user, and toggle Team admin on. They'll see the Admin tab in their team settings.
Team admins can also assign other team admins, but cannot remove org admins from team admin roles.
Users on multiple teams
A user can belong to more than one team. When they do, settings are evaluated per team for team-scoped features. For things that apply to the user globally (like which connections they can use), the most permissive applicable team setting wins — unless the org setting is Off, in which case Off always wins regardless of team.
Default team
When a user is created without a SCIM group mapping, they're placed in your org's default team. You can configure which team is the default in Organization → Teams → Default team. Users in the default team inherit all org settings with no team-level overrides unless a team admin changes them.
Team-level assistant configuration
Each team can have its own assistant configuration — a different name, persona, or set of skills — set by the developer via the platform. Org admins cannot change the assistant's underlying model or capabilities, but team admins can control which skills are installed for their team's assistant via the skills settings.