Understanding Group (Site) Tags

Primary Role: Business Administrator (BA)
Focus: Learn

Where: Admin Portal

🧭 Before You Start

This article is a reference to help you design and understand Group (Site) tagging strategies.
Use it before creating, editing, or bulk-updating Group Tags.

🎯Why It Matters

Group Tags are the primary mechanism for hierarchy rollups
They enable flexible, organization-specific reporting
Tags support scalability as organizations grow or reorganize

⏱️When to Use This

Designing your site hierarchy
Preparing reporting rollups
Aligning ANVL with other systems for analytics
Adding new Groups (Sites)

📝 What Group Tags Are

Key:value metadata applied at the Group (Site) level
Used to describe organizational context
Fully customizable per organization

Group Tags do not control:

User access
Permissions
Workflow availability

Using Group Tags for Custom Hierarchy Rollups

Rather than enforcing fixed fields, ANVL allows you to define tags that reflect your organization’s structure, such as:

Business units
Regions
Operating areas
Programs
Subsidiaries

Example (illustrative only):

[   { "businessUnit": "Manufacturing" },   { "region": "Midwest" },   { "operatingGroup": "Plant Operations" } ]

The tag names and values are defined by your organization.

Required Group Tag: `groupType`

The groupType tag is required for all Groups
Used for reporting and deployment logic

Accepted values

UAT – Demonstration or testing sites
PROD – Live operational sites

Benchmark Gensuite Alignment (If Applicable)

Group Tags do not control integrations between ANVL and other Benchmark Gensuite applications.
However, they can be used to support consistent reporting and aggregation across platforms, especially when building custom reports.

For organizations using ANVL alongside other Benchmark Gensuite applications, Group Tags may be used to:

Align site hierarchy concepts across platforms for reporting consistency
Support custom reporting and rollups that span ANVL and other applications

Common examples (naming conventions vary by organization):

bmgsOrg
bmgsSubOrg

Tags that are intended to support cross-platform aggregation or enterprise reporting should be reviewed with Subscriber Support or your account representative to ensure they align with reporting and data models.