Skip to content

Teams ​

A team is a smaller group of people inside your workspace, so the right folks stay together.

Why use it ​

Teams let you split a big workspace into smaller circles — for example by region, by product, or by client. That way each group sees and works on what belongs to them.

Step by step ​

Open Teams

Go to your workspace settings and click Teams. You will see a list of the teams you already have (it may be empty at first).

Create a team

Click New team, give it a clear name (like "Sales" or "North Region"), and save. The team now appears in the list.

Add people

People are invited to the workspace, not to a team — the workspace is what shares channels, posts and the calendar. Open Settings → Workspace and send the invite from there. See Invitations.

TIP

Pick names you'll still understand in six months. "Client A" beats "Team 2".

Good to know ​

  • A team always lives inside one workspace — it never spans across workspaces.
  • A team has no invite of its own; it groups permissions, and the members list shows its owner.
  • Invitations are a workspace feature and work today — see Invitations.
For developers

Teams are managed under /api/v1/teams (list, create, update, delete) with members at /api/v1/teams/:id/members. Every one of those is scoped to the caller's own teams — a foreign id returns 404. POST /api/v1/teams/:id/invite exists and returns 501: team-level invitations are not implemented, and the workspace invitation flow (/workspace/invite) is the one that works. A team record holds user_id (creator), name, owner, a permissions string array, and a free-form data object.