Skip to main content

Understanding User Records in ANVL

Learn how User Records are structured in ANVL and how identity, access, hierarchy, and metadata work together.

Lauren Baird avatar
Written by Lauren Baird
Updated this week

Primary Role: Business Administrator (BA)
Focus: Learn

Where: ANVL Manager, Admin Portal


🎯Why This Matters

User Records control access, reporting, hierarchy, and workflow visibility across ANVL.
Understanding how these fields relate prevents misconfiguration, failed updates, and reporting inconsistencies.


📝What a User Record Represents

A User Record represents one person who can access ANVL.

Each record connects:

  • Who the user is

  • What they can access

  • Which sites they belong to

  • Who they report to

  • How they appear in reporting

This understanding is essential before making changes in the Admin Portal. (More details: User Fields Reference)


Where User Records Appear
User information is visible in two primary places:

User profile view from the ANVL Manager Users tab.

User record view from the Admin Portal User Management tab.


What a User Record Includes (High-Level)

Every User Record stores information in these four areas:

  1. Identity & Contact Details

  2. Roles & Permissions

  3. Supervisor & Group Access

  4. Metadata for Reporting

These fields determine what the user can access, how they appear in reporting, and how ANVL connects them to your hierarchy.


Core Parts of a User Record (Conceptual)

Every User Record includes four major components:

1. Identity & Contact Details

Defines who the user is and how ANVL communicates with them.

  • Name

  • Email

  • Phone number

  • Preferred language

  • Username (authentication)

These fields affect login, notifications, and display across the platform.

Identity & Contact details in the user profile view from the ANVL Manager Users tab.

Identity & Contact details in the Admin Portal User Management table.


2. Roles & Permissions

Controls what the user can do.

  • Product access (ANVL Mobile, ANVL Manager)

  • Special Rights (Workflow Management, Super Admin, Risk Insights)

  • User management permissions

Permissions determine visibility, workflow access, and administrative capability.

Product access can be viewed and editing in the user profile in ANVL Manager. Special Rights, "Can Modify User," and "Hidden" can only be viewed and edited in the Admin Portal.

All permissions, Special Rights, and user settings can be viewed and edited in the Admin Portal User Management table. Hidden users can only be viewed here, not in the ANVL Manager Users tab.


3. Supervisor & Group Access

Defines organizational structure and scope.

  • Supervisor assignment (hierarchy and accountability)

  • Group (Site) membership

  • Primary Group

These relationships drive reporting, oversight, and workflow visibility.

See Understand Groups (Sites) in ANVL

Locations (Groups) and Supervisor assignments can be easily managed directly from the user profile in ANVL Manager.

Note: You can only assign users to Groups you have access to from this screen. Groups you do not have access to will appear in gray.

Admin Portal user management view where Business Administrators can assign users to any Group, regardless of their own Group access.


4. Metadata for Reporting

Optional attributes used for analytics only.

  • Tags (e.g., Job Title, Department)

Tags do not grant access or permissions.

User tags are only visible and editable in the Admin Portal User Management tool and not in the Users tab.


System-Generated Identifiers (Awareness Only)

Some User Record fields are created automatically and cannot be edited:

  • User ID

  • Sub (UUID)

  • Created / Updated timestamps

These identifiers power internal relationships between users, Groups, and reporting.

The user’s UUID appears at the end of the URL when viewing their profile in ANVL Manager.

System-generated identifiers and timestamps in the Admin Portal User Management table.


Why Understanding User Records Matters

  • Ensures accurate updates and bulk actions

  • Prevents access and hierarchy errors

  • Supports clean reporting and HRIS alignment

  • Reduces failed edits and rework


Related Articles


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


Did this answer your question?