Skip to main content

What is a user record in ANVL and how does it work?

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

Written by Lauren Baird

Answer

A User Record represents one person in ANVL. It brings together the information that defines who the person is, what they can access, where they sit in the organization, and how they appear in reporting.

At a high level, every User Record includes four main parts:

  • Identity and contact details

  • Roles and permissions

  • Supervisor and Group access

  • Metadata for reporting

These parts work together to determine:

  • how the user signs in

  • what they can do

  • which Groups they can see

  • who they report to

  • how they appear in analytics and reporting

You can see parts of the User Record in both ANVL Insights and the Admin Portal, but the Admin Portal shows the full record, including advanced permissions, tags, and system metadata.


Steps

Review the user in ANVL Insights

  1. Open ANVL Insights.

  2. Go to Users.

  3. Open the user profile to review day-to-day settings such as contact information, product access, supervisor assignment, and Group access.

User record view from the Admin Portal User Management tab.

Review the full record in the Admin Portal

  1. Open the ANVL Admin Portal.

  2. Go to User Management.

  3. Open the user record.

  4. Review the full set of fields, including advanced permissions, special rights, tags, and system-level identifiers.

User profile view from the ANVL Manager Users tab.

Understand the four main parts of a User Record

1. Identity and contact details
These fields define who the user is and how ANVL communicates with them.

Common examples:

  • first name

  • last name

  • email

  • phone number

  • preferred language

  • username

These fields affect login, notifications, display name, and communication behavior 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 and permissions
These fields control what the user can access and do.

Common examples:

  • ANVL Workflows access

  • ANVL Insights access

  • special rights such as workflow management or admin-level access

  • user management permissions

These settings determine whether the user can complete workflows, review data, manage users, edit workflows, or access advanced tools.

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 and Group access
These fields define the user’s place in the organization and the scope of their visibility.

Common examples:

  • assigned supervisor

  • Group membership

  • primary Group

These relationships affect reporting lines, workflow visibility, oversight, assignment behavior, and access to site-level data.

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
These are optional attributes used mainly for reporting and analytics.

Common examples:

  • tags such as job title

  • department

  • business unit

  • region or other reporting metadata

These fields help group and filter users in reporting. They do not usually grant access by themselves.

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

Understand system-generated fields
Some parts of the User Record are created by the system and are not meant to be edited.

Common examples:

  • user ID

  • UUID / sub

  • created timestamp

  • updated timestamp

These fields support internal relationships between users, Groups, permissions, 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.

Helpful notes

  • ANVL Insights shows the user record for day-to-day management.

  • The Admin Portal shows the most complete version of the User Record.

  • A problem in any one part of the User Record can affect login, permissions, reporting, or supervisor relationships.

  • User tags support reporting but do not normally control access.

  • System Managers should review changes carefully, because updates to user records can affect live access and reporting immediately.



Did this answer your question?