Teams

Teams group users. Reference: TEAM-1, etc.

Creating

1. People > Teams
2. Create Team
3. Name and describe
4. Set team leader
5. Add members
6. Save

Team performance

Each team page shows a performance card with work orders assigned and completed, completion rate, and assigned/completed tasks for the chosen period, so you can compare output across teams.

Locations a team can access

In the team form, "Locations this team can access" grants the team one or more locations. Members whose role uses Team scope data visibility then see the assets, work orders, requests and preventive maintenance in those locations, in addition to the records assigned to the team itself. Sub-locations are included automatically, so granting a building covers each of its floors.

A user whose role uses Team scope but who belongs to no team is not restricted at all — they keep seeing every record their permissions allow. Their detail page flags this so you can add them to a team. The role editor flags it as well, the moment you pick Team scope on a role that would restrict no one.

Team leaders and sub-teams

A team can sit under a parent team (People > Teams > Org Chart). With Team scope data visibility, the leader of a team also sees the work orders, assets, requests, preventive plans and inspections of every team under it, at any depth, and can assign work in them. A plain member of the parent team does not. To give a department head the work of all the crews under them, make them the leader of the parent team: there is no need to add them to every sub-team.