Teams

Teams (/teams) groups members of an organisation into working units — Alpha Team, Drone Section, Night Watch, Incident-Command — so a mission can be staffed by selecting a team rather than ticking every operator. A team on the Tactical plan maps to one of the three maxSubUnits slots; Command gets ten; Sovereign is unlimited.

Anyone with admin or above can create and edit teams. Managers can change members of teams they lead but cannot create new teams.

The team list

Column	Source	Notes
Name	`Team.name`	Shown on the mission staffing panel.
Leader	`Team.leaderUid`	Decorated with a star badge.
Co-leaders	`Team.coLeaders[]`	Optional secondary leads.
Members	member count	Click to expand the roster.
PTT channel	`Team.pttChannelId`	Auto-created on team save.
Last activity	derived	Timestamp of the team’s most recent mission.
Actions	—	Edit, delete, duplicate.

Click New team to open the create form.

Create team

The form captures: Name (required), Short code (2–4 chars, e.g. ALP, used on map callsigns and PTT roster), Colour (12-swatch palette), Description, Leader (required), Co-leaders (optional), Initial members (multi-select).

On save, ARGUS creates:

/organizations/{orgId}/teams/{teamId} — the team doc.
/organizations/{orgId}/teams/{teamId}/members/{uid} — one per member with role of leader, coLeader, or member.
A PTT channel at /taclink/channels/{channelId} named team-{shortCode} — members auto-join when the app starts.

Team profile

Clicking a team opens the detail pane. Tabs across the top:

Members

The roster: avatar, call sign, role within the team, and when they joined. Add / remove members inline (popover-confirmed on remove). A member’s org role is shown as a badge next to their team role — you can have an observer as an operator-level team member, but the Firestore rules still gate them on the stricter of the two.

Deployment history

Chronological list of missions that staffed this team. Each row shows the mission name, start time, duration, and a link to the mission report. This comes from a query on missions where teamIds[] contains the team ID.

Defaults

Team-level overrides for mission defaults. Anything you set here takes precedence over the org defaults on Organizations but can still be overridden per-mission:

Default PTT channels — list of channel IDs joined alongside the team channel.
Default venue — pre-selects a venue when the team creates a mission.
Default feature flags — turn AI copilot / live subtitles / E2E on or off for this team.
Required assets — list of assets that must be checked out before a mission can start (bodycams, radios, drone batteries).

Leadership

Promote / demote leaders. A team must always have one leader; removing the current one requires you to promote a replacement first. Co-leaders can start missions and edit the team roster but cannot delete the team.

Deleting a team

Trash icon on the team row, popover-confirmed. Deletion:

Soft-deletes the Team doc (deletedOn timestamp, remains queryable by historical missions).
Retires the PTT channel — messages are kept but no new traffic is accepted.
Emits admin.team.deleted into the audit stream.

Historical missions that staffed the team keep working — the team name is cached on the mission document so reports still render correctly.

Using a team at mission-create time

On the mission-create wizard, a Staff from team picker lists every team in the org. Selecting one pre-fills the operator list with the team roster and applies the team defaults; you can then add or remove individual users from that pre-fill.