Team settings

Settings → Workspace → Teams. Page title: 'Teams'. Subtitle: 'How your workspace is organized, and who sits in each team'. Shows every team in a table with Team Name, Owner, Members and Created columns. Teams with sub-teams have an expand arrow. The page is for org admins and owners; anyone else does not see the row.

'Search for teams' matches team names and owners. Known issue: it only finds top-level teams, so searching for a sub-team's name shows 'No teams match your search.' Expand its parent team instead.

Creating a team #

1. 1
   Click Create team (top-right)

   Opens the 'Add new team' dialog.
2. 2
   Name it

   A name is required, up to 100 characters. A description is optional, and takes the same formatting as a goal's (lists, a toolbar on selected text, emoji, and / to link a goal); it shows formatted on the team's page and has no @ mentions, since a team description notifies nobody. Renaming a team later is safe: references update automatically.
3. 3
   Pick the owner and, optionally, a parent team

   The owner starts as you; pick someone else if they lead the team. The owner joins the team as a Team Admin. Pick a Parent team to make this a sub-team; nested teams are listed with their path (for example 'Product › Design').
4. 4
   Click Add Team

   You see 'Team created successfully'. A team view is created automatically at /views/teams/<teamUuid> and appears under Teams in every team member's sidebar. Add members from the team's page (see below).

Editing a team #

Each row's ⋯ menu has Edit team, Manage members and Delete team. Edit team opens a dialog to change the name, description, owner and parent team; a team cannot be moved under itself or one of its own sub-teams. Update Team saves it ('Team updated successfully'). Manage members opens the team's own page (route /settings/teams/<teamUuid>), where you add and remove members, change their team roles, add sub-teams and fill in the team's Memory. See Team detail.

Transferring team ownership #

On the team's page, the current team owner can hand the team to another member: open that member's role selector and choose Team Owner. A confirmation warns that the transfer can't be undone (only the new owner can transfer it back). Transfer ownership makes that member the owner and, as the dialog says, makes you a Team Admin. Team Admins can't do this. An org admin can also change the owner from Edit team.

Known issue: the previous owner currently ends up as a Team Member, not a Team Admin. Change their role back to Team Admin on the team's page if they should keep it.

Deleting a team #

From the row's ⋯ menu → Delete team. Deletion removes the team and its team view and cannot be undone. Sub-teams are not deleted: they become top-level teams unless you delete them separately.

If the team owns any goals, the delete dialog asks what to do with them first. You must choose one of: Reassign to another team (pick a team; the goals stay team-owned), Make them Company goals (the default: they become organization-level, no-team goals and stay visible in company filters), or Delete these goals (permanently deletes each owned goal and all of its sub-goals). This prevents owned goals from being stranded as team goals with no team, which would hide them from every team filter.

To delete several at once, tick their rows and choose Delete teams. Brev then asks about each team that owns goals in turn, with the same three choices; switch on Apply to all to use your current choice for every remaining team. Nothing is deleted until you confirm the last step, and any team that fails to delete stays selected.

Structure tips #

• Mirror your real reporting structure. Don't invent a parallel one just for Brev.
• Keep teams shallow. Three levels deep is plenty.
• Renaming a team is safe; references update automatically.