Users, teams and departments

Optimetrix has three levels of structure. Get them right once and every report inherits them.

LevelWhat it is
UserOne person, tied to the device(s) running the agent under their account.
TeamThe unit most reports roll up to — a squad, a pod, a shift.
DepartmentA grouping of teams — Engineering, Support, Operations.

Tips

  • Model teams the way work actually flows, not the org chart, if the two differ.
  • A user can move between teams; historical data stays attached to the team they were in at the time.
  • Look up a person by name or email in the app to find their user record — don't rely on a list.

Did you find this article useful?

  • App types and categories

    Every application and website the agent sees is classified into a category through an app type mappi...
  • Working hours and available time

    Utilization is active time on planned work ÷ available hours. The denominator only makes sense if Op...
  • Projects

    Projects are an optional layer above categories for teams that want utilization and workload split b...
  • Roles and who sees what

    Access in Optimetrix is role-based. Configure it before you invite managers. RoleTypical scope Emplo...