Skip to main content

Understanding User Records in ANVL

This article explains the different parts of a User Record in ANVL and what each field means. You’ll learn how users are identified, how their access is controlled, and how supervisor and Group assignments work.

Lauren Baird avatar
Written by Lauren Baird
Updated yesterday

A User Record represents a single person who can access the ANVL platform. Each record stores the user’s identity, permissions, Group memberships, supervisor relationship, and optional metadata. Understanding these fields is essential before making updates in the Super Admin Panel.


User Record in the Insights Users tab:

User Record in the Amin Panel User Management Tool:


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.


1. Identity & Contact Details

These fields define who the user is and how ANVL communicates with them.

Field

Description

Impact

First Name / Last Name

User’s display identity

Appears across the ANVL platform

Email

Primary login address for SSO

Incorrect emails prevent login

Phone Number

User’s mobile contact

Required for SMS notifications

Preferred Language

IETF language code (e.g., en-US, fr-FR)

Controls in-app text and notifications

Username

Login credential (SSO-linked)

Not editable; used for authentication

Users tab:


Admin Panel User Management Tool:


2. User Identifiers (System-Level)

These values are created automatically and cannot be edited.

Field

Purpose

Notes

ID

Primary system identifier

Required when assigning supervisors

Sub (UUID)

Database unique identifier

Used in the database as the unique identifier

Created At / Updated At

Timestamps in UTC

Used for tracking account history

These IDs drive behind-the-scenes logic that connects users to supervisors, Groups, and reporting.

Users tab:

Admin Panel User Management Tool:


3. Roles & Permissions

Roles define what the user can do inside ANVL.

Role / Setting

Meaning

Impact

TECH

Frontline mobile role

Can complete workflows

ADMIN

Manager role

Can view analytics, assignments

Can Modify User

Grants access to the Users tab

Allows admins to manage other users

Hidden

Marks testing/IT accounts

Hides from assignment lists, dashboards

Permissions determine visibility, workflow access, and administrative capabilities.

Users tab:
Note: "Can Modify User" and "Hidden" are not viewable nor editable in the Users tab. These fields can be viewed and edited in the Admin Panel User Management tool.



Admin Panel User Management Tool:


4. Supervisor Assignment

Each user can be connected to a supervisor by using the supervisor’s integer ID.

Field

Description

Impact

Supervisor

The ID / Name of the user’s manager

Controls oversight, reporting, and engagement tracking

This relationship ensures accurate activity monitoring and workflow accountability.

Users tab:


Admin Panel User Management Tool:


5. Group Access (Division IDs)

Users can belong to one or many Groups (sites).

Field

Meaning

Impact

Division ID

User’s initial / primary Group

Default group in Workflows

Division IDs / Locations (Group)

All Sites the user can access

Grants visibility and permissions

Users tab:


Admin Panel User Management Tool:


6. Tags (Metadata for Reporting)

Tags store optional, reporting-only user metadata.

Example

Use

{ "Job Title": "Technician" }

HR/role reporting

{ "Department": "Field Service" }

Analytics filtering

Tags do not affect access or permissions.

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


Why Understanding User Records Matters

  • Ensures accurate updates when managing users

  • Prevents misassignments that affect reporting or access

  • Helps admins troubleshoot login, visibility, or workflow issues

  • Supports clean, reliable HRIS and operational data

Did this answer your question?