Documentation — Teams and scope

Getting started

Teams and scope

How teams organize everything in SmartRetro, how the team switcher sets your scope, and what archiving a team actually does.

Everything in SmartRetro — retros, signals, action items — belongs to a team. The team switcher at the top of the sidebar decides what you’re looking at, everywhere in the app.

The team switcher

With one team, the switcher is just a label: your team’s name, marked Your team. Nothing to manage.

With more than one team, it becomes a dropdown. All my teams sits at the top, followed by each team with its open-signal count (“12 open signals”). Teams with high-severity signals show a red badge — the “needs you now” count — so you can see at a glance which room is on fire before you walk in. The bottom of the menu has Manage teams and New team shortcuts.

Your choice is sticky: switch to a team and every page — dashboard, signals, retros, action items — stays in that team’s scope until you switch again. The scope also lives in the URL as a ?team= parameter, so a link you share opens in the same scope you were looking at.

Knowing where you are

Team-scoped pages show a scope kicker above the content: the team’s name with its accent color, or All my teams with a layers icon and a “teams · aggregated” note. Each team gets a stable color, used consistently in the switcher and on team chips, so aggregate views stay scannable.

In All my teams, every row is tagged with a team chip. Signals that haven’t been routed to any team (see below) are tagged Org-wide.

The Listening card

Below the navigation, the sidebar shows a Listening card — an honest answer to “what is SmartRetro actually reading right now?” When sources are connected, it lists the mapped channels for your current team and the signal count for the last 14 days. If a team has no channels mapped, it says so, and notes that unmapped sources route org-wide. With no sources at all, it reads Not listening yet, and admins get a Connect link. It never implies coverage you don’t have.

How signals reach a team

Signals are routed to teams by channel mapping: a Slack channel mapped to a team sends its signals to that team’s feed. Anything without a mapping lands in the org-wide pool, visible from All my teams. Details are in Signals.

Managing teams

The Teams page (also reachable via Manage teams) is where teams are created and edited. A team has a Title, an optional Description, an Owner, and a Status (Active, On Hold, Completed). Plans include a set number of active teams; at the limit, the New Team button shows Limit Reached — see pricing.

Archiving

Workspace admins can archive a team. Archiving is not deletion: every retro and action item is retained, and the Teams page shows the team in an Archived teams section marked “History retained · not billed.” Archived teams leave the team switcher and free up an active-team slot on your plan. If the team comes back, Reactivate restores it — history intact.

Where to go next

Teams shape who sees what; people shape who’s in them. See Inviting your team for members and roles, and Running a retro for what a team actually does together.