Skip to main content

Teams

Premium feature

A team is the shared workspace of a group of people, such as a department. It has members with roles, its own projects and a selection of agents its members can chat with. Teams are not the same as swarms: a swarm is a group of agents, a team is a group of people.

Teams are enabled per instance. Until the feature is switched on you see neither the team interface nor the Teams admin page.

How sharing agents changes with Teams (the “Everyone” team, join links, ChatBots for websites) is described in Sharing with Teams.

The Personal team​

Every user has a Personal team. It is created automatically, holds your existing projects and is only for you: it has no member management and cannot be deleted. Your agents, projects and chats work in it as before; sharing still happens per chat or project.

Switching between teams​

At the bottom left of the sidebar, the team switcher shows the current team (with its member and agent counts) and lists your teams. New team creates another one, if you are allowed to (see Who may create teams). Whoever creates a team becomes its admin.

Inside a team, the left side lists the Team chats (chats directly in the team) and the Projects in this team. Projects are optional topic folders inside the team.

With the Editor or Admin role you create one there with New project: a name, and optionally one of the team's agents; without an agent of its own, its chats use the team's default agent. Move to team… takes a project of your own into a team where you may at least edit. That works only when everyone with access to the project is in the team, and only your own chats are in it.

Members and roles​

A team consists of users and groups; when a group is a member, everyone in it belongs to the team (shown as "via group X"). Every member has a role:

RoleMay
Viewerchat with the team's agents; read shared files, projects and tasks
Editoradditionally create and change projects and tasks and upload shared files
Adminadditionally manage the team's members, agents, tools and credentials

A team always needs at least one admin, and the person who created it cannot be removed.

Invitations: on the Members tab, admins create an invitation link with a chosen role. Anyone with the link can join once, within 7 days. Open invitations can be revoked there; the link then stops working, and people who already joined stay.

Agents in a team​

A team uses only the agents granted to it. On the Agents tab of the team settings, admins add agents: ones an administrator has marked Available in catalog under Team catalog in the agent editor, plus agents they own or may edit; instance administrators can add any agent. When an agent is removed, members can no longer start new chats with it; existing chats stay readable.

A granted agent brings along the specialists wired into it as delegates (see Delegation).

For each new chat you pick which agent should help, with the team's default agent preselected (the picker is skipped when there is nothing to choose). The agent is fixed for the life of the chat. Continue with another agent in the chat menu starts a new chat with a different agent of the team, carrying the conversation over as context.

Chats stay private​

Chats in a team are private: you see your own chats and whatever others explicitly share with you. Team admins cannot read members' private chats and see no usage data such as the number or activity of chats, only members, roles, agents and configuration. If you leave a team you lose access to its chats; they are kept and come back if you rejoin.

Team settings​

Admins open the settings via Team settings (or, in the admin overview, via the team's row). The tabs are:

  • General: name, description, icon and default agent; the team can also be deleted here (confirmed by typing the team name). Its projects move to the deletion bin when the bin is on. With the bin off, a team that still holds projects, chats or files cannot be deleted (409); move or delete them first.
  • Members: people and groups, roles, invitations.
  • Agents: the agents granted to the team.
  • Tools & credentials: the team's tools and credentials; they come from the default agent, which an admin must set first.
  • Drive: a placeholder for the upcoming team drive.
  • Notices: write notices to your team or individual members, see Notices.

Only team admins can change these settings; everyone else sees them read-only.

Who may create teams​

Administrators can always create teams. Under Admin → Settings → Who may create teams they decide who else may:

  • Only administrators
  • Everyone
  • Members of selected groups

The setting is checked on every creation; removing someone from a permitted group stops them creating further teams but leaves existing ones alone. The Personal team does not depend on the setting.

The Teams admin area​

Under Admin → Teams (/admin/teams), administrators with the Manage teams permission (space:manage) see every team in the instance, with its type, members, agents and linked groups. From there they can create teams (with at least one admin as initial member; you do not become a member yourself), manage the settings and members of any team, and delete teams. The permission does not grant reading chats. When the feature is not enabled, the page shows a notice instead.

The routes behind this are described in the management API.