Skip to main content
Teams organize your hosts into a scoped hierarchy and control which hosts each user can see. A team owns a set of hosts; its members can see those hosts, and child teams are limited to a subset of their parent’s hosts. This page requires the manage teams permission and is available only with PostgreSQL-backed authentication (hidden in static admin mode).
A search bar at the top of the page (“Search teams, members, or hosts…”) lets you filter the team tree by team name, member username, or host identifier. Results update as you type.

Global Users

Global admins see a Global Users section at the top of the page showing users who are not assigned to any team. This section also displays top-level team and host counts across the deployment, giving admins a quick overview of unassigned users and overall team coverage.

Team cards

Each team in the tree shows:
  • An expand/collapse control (when it has sub-teams).
  • The team name.
  • A badge with its host count, and sub-team count when applicable.
  • An Admins row (the members whose role is admin or owner), and a member count.
If you can manage the team, a row of action icons appears: Show hosts & members, Add sub-team, Edit hosts, Rename team, and Delete team.
Renaming a team is done inline on the team card — click the rename icon, edit the name in place, and confirm. There is no separate drawer or dialog for renaming.

Detail panel

Show hosts & members expands a two-column panel:
  • Hosts: each assigned host with a status dot, its host ID, and host-type badge.
  • Members: the team’s members, each with their dashboard role badge.
Note that there are no separate per-team roles, a member’s badge reflects their global dashboard role, and a team’s “admins” are simply the members who are admins or the owner.

Creating a team

New Team (or Add sub-team on an existing team) opens a drawer:
  • Team name.
  • Parent team: Top level (Global) for a global admin, or a specific parent. A top-level team may include any host; a child team is limited to its parent’s hosts.
  • Hosts: once a parent is chosen, a host picker lets you select which hosts the team covers (search by name, ID, or type).
The team hierarchy has a maximum depth of 3 levels (top-level → child → grandchild). You cannot create sub-teams beyond this depth.

Assigning members

Members aren’t added on this page. A user’s team membership is set on the User Management page (when creating or editing a user). Team membership is what controls which hosts that user can see.

Host scoping and visibility

A few rules govern how host visibility works:
  • A team’s assigned hosts define which collectors its members can see.
  • A child team’s hosts must be a subset of its parent’s hosts. The host editor enforces this, and you can’t remove a host from a parent while a child team still uses it.
  • Editing a team’s hosts is done through Edit hosts (the host picker), then Save hosts.

Deleting a team

Delete team asks for confirmation, warning that members will lose access to that team’s hosts and that the action can’t be undone. A team that still has sub-teams can’t be deleted, remove or move its sub-teams first.
Last modified on October 8, 2026