App types and categories

Every application and website the agent sees is classified into a category through an app type mapping. Categories are what the dashboards group and colour by, so this taxonomy shapes every chart.

How it works

  • An app type is a rule that maps an application or domain to a category (e.g. "VS Code → Development", "*.zendesk.com → Support").
  • Categories are defined by your organisation. Their names are whatever you choose — they are often not in English.
  • Unmapped activity lands in a default / uncategorised bucket until you classify it.

Getting a clean taxonomy

  1. Start from the uncategorised list after the first few days — it shows what your teams actually use.
  2. Create 8–15 categories, not 50. Broad buckets read better.
  3. Re-check monthly; new tools appear.

Before interpreting a category on a chart, confirm what it maps to — the label alone can be misleading if the mapping is loose.

Did you find this article useful?

  • Users, teams and departments

    Optimetrix has three levels of structure. Get them right once and every report inherits them. LevelW...
  • 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...