Skip to main content

Understand the ANVL Org Hierarchy

Learn how ANVL’s organizational hierarchy is structured and how Groups (Sites) support reporting, assignments, and rollups.

Lauren Baird avatar
Written by Lauren Baird
Updated over 2 weeks ago

Primary Role: Business Administrator (BA)
Focus: Learn


🎯Why This Matters

ANVL reporting, assignments, and visibility follow a defined hierarchy.

Understanding this structure helps you:

  • Configure Groups correctly

  • Avoid reporting and assignment issues

  • Use Group Tags effectively for rollups and analytics


⏱️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 a fixed, logical hierarchy:

  1. Organization (your business)

  2. Group = Site

  3. Supervisor

  4. User

This hierarchy determines how work, reporting, and oversight flow through the platform.

Conceptual view of the ANVL organizational hierarchy from Organization to User.


How Groups Fit in the Hierarchy

A Group represents a physical or logical site within your organization.

  • Users are assigned to one or more Groups

  • Supervisors connect Users for reporting and accountability

  • Groups are the level where:

    • Workflows are deployed

    • Workflow and Work Item Categories are configured

    • Assignments are scoped

    • Reporting begins

For more details see Understand Groups (Sites) in ANVL.

My Group dropdown in ANVL Manager used to select and switch between site-level Groups (sites).


Important Clarifications

  • The hierarchy itself is not configurable

  • Organizational rollups are achieved using Group Tags, not nested Groups

  • Group Tags describe where a site belongs within your organization (e.g., region, division, business unit)

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


How Reporting Uses the Hierarchy

  • All submissions are tied to a Group (site)

  • Reports and dashboards are filtered and aggregated by Group

  • Group Tags enable rollups across:

    • Regions

    • Programs

    • Business units

User Tags can be used when individual-level metadata is required. For more details see Understand User Tags.

Standard Power BI report filters showing Group mapped to Site and Job Title sourced from User Tags; additional hierarchy or custom filtering can be configured using Group or User Tags—contact your Benchmark Gensuite point of contact for customization needs.


Integrated Benchmark Gensuite Applications (High-Level)

For organizations that use ANVL alongside other Benchmark Gensuite applications, we recommend mapping ANVL Groups (Sites) to corresponding Benchmark Gensuite sites whenever possible.

This alignment helps ensure:

  • Consistent site structure across applications

  • Accurate reporting and data alignment

  • Reduced integration and synchronization issues

If your organization requires a different site configuration, work with your Benchmark Gensuite point of contact to assess requirements and understand potential impacts before making changes.


🔑Key Takeaways

  • ANVL hierarchy is fixed and logical

  • Groups represent sites, not nested org levels

  • Reporting and assignments start at the Group level

  • Group Tags are the primary tool for organizational rollups


⚠️Watch Out For…

  • Group hierarchy is flat by default

  • Rollups require consistent Group Tagging

  • Re-organizing Groups may impact:

    1. Reporting

    2. Assignments

    3. Integrations


🔗Related Articles


Job Role: Business Administrator | Permission Level: Admin / ANVL Web | Special Rights: Admin Portal

Did this answer your question?