Teams

A team in Scout HQ is a flat operating group inside one workspace — Sales, Production, Finance. The page states the division of labour in a line: "Teams answer who sees and claims work. Roles answer what a person may do."

Screenshot: Settings → Workspace → Teams.

Everyone, the one team you do not make

Everyone is created and maintained by Scout and marked SYSTEM: "Every active member. Safe company notices and the unassigned fallback." Nobody can be removed from it and it cannot be deleted, not even by the Owner. Work with no better home lands here, visibly marked UNASSIGNED — Scout being honest rather than Scout guessing.

Create a team

Open Settings → Workspace → Teams.
Choose New team.
Type a NAME, up to 80 characters. Use the small mark to the left of the field to choose an icon and colour, so the team is recognizable at a glance.
Fill in WHAT IT HANDLES, up to 180 characters. This is not decoration — the note under the field says it "Helps Scout route work to the right place and person", and Scout reads it when deciding where a new item belongs.
Tick the MEMBERS who should be on it. You are ticked by default, and Everyone membership is automatic so it is not listed here.
Choose Create team.

Only an Owner or Admin can create a team, change its sources, or move people. Members and Viewers can see which teams exist and who is on them.

Inside a team

Choose a team to open its own page. The header shows when it was created and by whom; the top card holds Icon & color, Team name, and What this team handles with Save changes.

A team detail page with its members, their primary-team tags, and the sources the team owns.

Members. The card carries a count and an Add member button. Its picker, ACTIVE WORKSPACE MEMBERS, holds active members of this workspace only — you cannot type an email address here, so invite the person first. The footer says when the change bites: "Access to this team's work starts when the membership is saved." Each row shows the person's workspace role, plus a PRIMARY tag when this is their primary team. The actions menu offers:

Make primary team — makes this the person's home team. A person can be on several teams but has one primary team.
Remove from team — confirms with "Removing name takes their access to team work with it immediately. Their seat, other teams, and Everyone membership stay unchanged."
Deactivate seat… — the whole-workspace action, in Changing roles, deactivating, and reactivating.

Sources this team owns. A source is one connected thing Scout reads: a mailbox, an accounting company, a supplier feed. Giving a team a source says "work out of here belongs to these people." Use Add source to move one onto the team, or Reassign to hand it to another team. Both dialogs name the consequence: the source and its unresolved queue move together, and settled history stays where it was recorded. Personal mailboxes never appear in these pickers. See Team-owned vs personal sources.

Archive this team. Archiving hides a team from pickers and keeps its history; members keep their other teams and Everyone. Scout will not archive a team that still matters: while it owns sources or has unresolved work the control reads Resolve team dependencies first and names what to clear.

Teams Scout proposes

Scout sometimes notices a group you have not made yet. Proposals sit at the top of the Teams page with the caveat attached: "Read from your connected sources, not from job titles. Nothing is created until you say so."

Each proposal shows a name, a likely-member count, and its evidence, labelled by where it came from — an accounting company with no owning team, a shared mailbox nobody owns. A SEATS line names the people involved and flags anything awkward, such as a proposed member who is a Viewer and would see the work without being able to act on it.

Read the evidence rows.
Choose Approve to create the team with that name, that description, and the likely members already on it — or Not a team to decline.

Scout proposes at most five teams, only where two people or a real shared source back it, and never creates one itself. Declining is a real answer — it stops Scout asking.

When nothing better matches

One switch sits at the foot of the page: Fall back to a person's primary team, on by default. "Used when Scout knows the person but not the work type. Off means fall straight to Everyone." Leave it on if your teams are meaningful; turn it off to make unrouted work pile up visibly in Everyone instead.

Good to know

Team membership decides who can Claim a piece of team work. Someone outside the team is greyed in the assignment picker, and the pairing is checked on the server, not by the list.
Being on a team never grants access to another person's personal mail. That always needs an audited visibility review.
A workspace with one person shows no scope pill and no team chips. Both appear the moment a second seat exists.
You can also name your first teams during the first-run setup of a new workspace, at the Teams step — those are real teams, created through these same controls.