Skip to main content

Understand the ANVL Org Hierarchy

Explains the core ANVL hierarchy and how Groups (Sites) fit into reporting and organizational structure.

Lauren Baird avatar
Written by Lauren Baird
Updated this week

Why It Matters

  • ANVL reporting and assignments follow a defined hierarchy

  • Understanding the hierarchy helps prevent misconfiguration

  • Group Tags are applied within this structure to support rollups


When to Use This

  • Getting familiar with how ANVL is structured

  • Planning site setup or re-organization

  • Reviewing reporting relationships


ANVL Hierarchy (Conceptual)

ANVL uses the following hierarchy:

  1. Organization (Business)

  2. Group = Site

  3. Supervisor

  4. User


How Groups Fit in the Hierarchy

  • A Group represents a physical or logical site

  • Users are assigned to one or more Groups

  • Supervisors connect Users for reporting purposes

  • Groups are the level at which:

    • Workflows are deployed

    • Categories are configured

    • Reporting begins


Important Clarifications

  • Hierarchy structure itself is not configurable

  • Organizational rollups are achieved using Group Tags

  • Group Tags describe where a site belongs within your organization

For details on how to use Group Tags to model your hierarchy, see Group (Site) Tags.


Watch Out For…

  • Group hierarchy is flat by default

  • Rollups require consistent tagging

  • Re-organizing sites may impact reporting and integrations


What You Should See

  • ANVL Groups aligned at the site level

  • Group Tags used to model organizational hierarchy and reporting rollups

  • User Tags applied where individual-level metadata is needed

  • Work Folders (if applicable) used to support additional hierarchy levels and aggregation

Did this answer your question?