Workspaces and teams

An org has workspaces. A workspace has teams and features. Each one has its own Admins, Managers and Users.

Workspaces

A workspace groups the teams and features that work together inside an org. For example, one workspace per product area: "Payments", "Onboarding".

  • Every feature lives in one workspace.
  • Every team sits in one workspace.
  • A new org gets its first workspace by itself.

Create a workspace

Org Admins and Managers create workspaces. The org, or its company, can leave this to org Admins only. See Settings.

  1. Open your org: the Orgs tab in the left menu, then the org. Or click + New workspace in the left menu.
  2. Click Create workspace (or the dashed New workspace card).
  3. Type a name. Optionally, add who runs it: pick people from the org as Admin or Manager.
  4. Click Create workspace. SeamTrail opens it.

An org Admin runs every workspace already. An org Manager who creates a workspace becomes its Admin.

A workspace's page

Open a workspace to see:

  • Teams: each team, who its Admin is, and how many people and features it has. Admins and Managers of the workspace create teams here.
  • Features: the features in the workspace. Those who run the workspace see all of them; everyone else sees the ones they are on.

Teams

A team is a group of people who build things together, like "Backend" or "Checkout". A team sits in one workspace.

Teams show up inside features as team folders. A team folder shows that team's tickets and how far their code has gone.

SeamTrail can also create teams for you. When you accept ticket suggestions, SeamTrail reads each ticket's team from Jira. If that team is new, it creates it in the feature's workspace.

Create a team

Admins and Managers of a workspace create its teams. The workspace, or a level above it, can leave this to its Admins only. See Settings.

  1. Open the workspace.
  2. Click Create team (or + New team in the left menu).
  3. Type a name. Team names are unique in the org.
  4. Optionally, add who runs it. Then click Create team.

A workspace Manager who creates a team becomes its Admin. Workspace Admins run every team in their workspace already.

A team's page

Open a team to see:

  • People: who is in the team, with their role.
  • Where its work lives: its Jira project, Confluence space, Slack channel and code repository. SeamTrail reads these places for every feature of the team.
  • Features: the features the team works on.

People in a workspace or a team

Each workspace and team has its own Admins, Managers and Users. Open its Settings → People.

WhatAdminManagerUser
See who is in it✓✓—
Add someone from the org as User or Manager✓✓—
Add someone as Admin✓——
Invite someone new by email✓✓—
Change someone's role✓——
Remove a User✓✓—
Remove an Admin or a Manager✓——
Leave✓✓✓

Rank goes down, never up:

  • An org Admin is Admin of every workspace and team in the org. An org Manager is their Manager.
  • A workspace Admin is Admin of every team in that workspace. A workspace Manager is their Manager.
  • A team role gives nothing above the team.

Someone added to a team joins the team's workspace as a User too. Someone removed from a workspace also leaves its teams.

Invite someone by email

  1. Open the workspace's or team's Settings → People.
  2. Under Invite by email, type the email and pick a role.
  3. Click Invite.
  • Someone new gets an invite email. They join the org as a User, and the workspace or team with the role you picked, when they first sign in.
  • Someone who already has a SeamTrail login is added right away.
  • Someone already in the org is added to the workspace or team right away. An invite never lowers a role they already have there.

Settings of a workspace or a team

Click Settings on its page. See Settings.

The Permissions tab decides who can bring people in and, in a workspace, who can create teams and features. A workspace or team follows the level above unless its Admin picks something else. See How settings pass down.

Delete a workspace or a team

Admins can delete them, in Settings → General.

  • A workspace can be deleted only when it is empty: delete its teams and move its features first.
  • A team can be deleted only when no feature uses it.

On this page