Skip to content
ARGUS User Manual

Teams tile

The Teams tile is the mission-scoped version of team management. Org- level team templates live under Admin → Teams; this tile lets commanders spawn mission-specific teams, assign operators, and assign tactical roles.

What you see on each team card

  • Team name + optional callsign.
  • Colour stripe — the team’s accent colour (pick from 10 swatches).
  • Member avatar dots — first 5 members as circles with initials, plus a “+N” overflow badge for more.
  • Member count.
  • Description preview — truncated to a few dozen characters.

Expanded view (click card):

  • Full description.
  • Member list with per-member role badges:
    • Leader — star icon.
    • Member — person icon.
    • Support — build / wrench icon.
  • Edit + delete action buttons.

Creating a team

Click New Team. The form:

  • Name (required).
  • Callsign (optional; shown in chips + on radio).
  • Colour — pick from 10 preset swatches.
  • Description — free text.

Once the team exists you add members:

  • A dropdown lists unassigned assets (operators not yet on any mission team).
  • Pick a user + pick a role (Leader / Member / Support).
  • Click add.

Repeat for more members. The team can have any number of members.

Editing

Click the pencil on a team card:

  • Change name / callsign / colour / description.
  • Re-order members via drag-handle buttons.
  • Change a member’s role inline.

Saves flow immediately to Firestore; all participants see updates in real-time.

Deleting

Popover confirmation removes the team and all member records. Hard delete — no undo.

Quick-role-change

In the expanded card, clicking a member row reveals a quick role picker without opening the full edit form. Useful during operations when you need to promote a Member to Leader without interrupting flow.

Persistence

Firestore: missions/{missionId}/teams/{teamId}. Members are stored as a nested array on the team doc. Changes are audit-logged to blackbox.

Permissions

No explicit commander-only check in the current UI — any mission participant can create, edit, or delete teams. This is an aspirational gap; role-based gating is planned but not enforced.

Interaction with other tiles

  • Fleet tile — member assignment in the teams tile reflects in any fleet filter that respects team membership.
  • Tasks tile — tasks can be assigned to a team; team members inherit.
  • Timeline — team creates / deletes / role-changes are logged as events.

Known limitations

  • No permission gating on team CRUD.
  • No cross-mission team templates from here (use Admin → Teams for that).
  • No “leave team” self-service — the team admin must remove you.
  • Callsign isn’t unique-validated — two teams can share a callsign.