Profiles and Profile Groups

In this article, we explain how profiles and profile groups work for Regula IDV Platform, including their structure, configuration, and access management.

• Profile
• Profile Groups
• Access Control
• Profile List
• Profile Data Structure
• Populating Profiles and Groups

Profile

A profile is a collection of facts about a person. It includes the following data fields:

Profile Field	Content
Data	A set of required individual attributes.
ID Documents	A set of identity documents that belong to the person and are processed via Regula Document Reader SDK.
Biometrics	A set of biometric data: selfies, fingerprints, and retinal images.
Screening	A list of all matches between the analyzed profile data and compliance watchlist entries from the screening providers (LexisNexis).
Attachments	A collection of arbitrary binary files associated with the profile (photos and documents processed outside Regula Document Reader SDK).
Sessions	A list of all sessions linked to the profile.
Geolocation	The complete history of geolocation and IP location data associated with the profile.
Devices	The complete history of the devices used in completing sessions.
Comments	A list of comments related to the profile status changes.
Timeline	The complete history of creation and modification of all profile data.

Profile Groups

Profiles can be organized into groups—collections of profiles that share a common data structure. The purpose of grouping is to align profiles with business requirements.

You will benefit from grouping if:

• You need specific sets of required fields that may vary depending on the business process.
• You want to enforce access control so that only certain roles can view or edit specific profiles.

Profile groups are available in a separate Platform portal module. To view profile groups, open the corresponding Profile vertical menu tab, which contains the table with brief details:

Column	Description
NAME	The profile group name.
DESCRIPTION	An arbitrary description of the profile group.
QUANTITY	The number of profiles within the corresponding group.

Configuration

When creating or editing a profile group, the following parameters are defined:

Parameter	Description	Requirement
Name	The group name, displayed in the overview Profile Groups table.	Required
Description	A detailed explanation of the profiles group purpose and content.	Optional
Attributes	A set of fields, displayed in the profile group for the default All UI view.	Required
Title	A set of data fields, displayed as the title for each profile within the group.	Required
Summary	A set of data fields, displayed in the summary section for each profile within the group.	Optional
Track Device	Whether to capture and preserve the device information in the profile during a session run.	Optional
Track Location	Whether to capture and preserve the geographic and IP location in the profile during a session run.	Optional

Attributes

Attributes are the fields that can be filled in each profile. Their type and number depend on the business process.

Each attribute is defined by the following parameters:

Parameter	Description	Requirement
ID	A unique string identifier of an attribute.	Required
Name	An attribute's name (a human-readable title).	Optional
Description	An arbitrary brief description of the attribute contents and purpose.	Optional
Type	One of the supported attribute data types: general (default)—free text, suitable for most cases date—formatted date email—email format phone—phone number format document—document file (processed by the Document Reader SDK) biometrics—biometric-related photos binary—arbitrary binary file	Optional
Unique	Whether the attribute's value must be unique within the entire profile group.	Optional

Summary

Summary is a set of fields displayed in the profile’s summary section. Only fields from attributes can be selected, and only text-based fields are supported (so document, biometrics, and binary types are excluded).

Views

Profile views are customizable tables that show the brief information about profiles within the group. These views work like session views. By default, only the All view is available and activated; it represents the profiles' statuses and all their attributes, configured during the profile group creation.

To create, edit, activate, or deactivate profile views, open the corresponding profile group and click the Manage Views button.

Profile views can be configured with:

• Title
• Description
• Columns
• Sorting
• Filters

Access Control

To work with profiles, the profile reviewer role is required.

• The profile reviewer has access to profiles and sessions.
• By default, the profile reviewer can access only the default group. Access to other groups must be explicitly granted.
• The profile reviewer can only view groups, but cannot create, edit, or delete them.
• The profile reviewer can create custom views within groups.

Access management for profile groups works similarly to access control for views and workflows.

Within a group, a user has access to all profiles, but specific actions can be restricted:

• Create a profile
• View a profile
• Delete a profile
• Change a status
• Edit data
• Load data
• Start additional verification from a profile
• Export the profile
• Download attachments

For more details, see the User Management page.

Profile List

The profile list is a table where each row represents one entry within the selected profile group. The list behaves like a view that can be configured with filters, sorting, and custom columns.

The Status column is always present and displayed first. See available profile statuses in the following table.

Status	Description
PENDING	The profile is waiting for another status to be assigned.
APPROVED	The profile has been reviewed by an operator and approved as eligible.
REJECTED	The profile has been reviewed by an operator and rejected as ineligible.
SUSPENDED	The profile has been put on hold before it is approved or rejected by an operator.

Profile Data Structure

The profile screen UI is divided into two vertical sections:

• The summary section
• Information tabs

The upper profile summary section acts similarly to the session summary. See the details in the following table.

Data	Description
Title	A composite field that includes one or more profile attributes selected during the profile group creation or editing.
Photo	The last uploaded biometric photo.
Field set	A set of text-based attributes selected during the profile group creation or editing.
CREATED AT	The timestamp of the profile creation.
LAST UPDATED	The timestamp of the last profile modification.

The lower section contains a set of information tabs. The Data tab is open by default.

Data

The Data tab contains all field data except documents, photos, and binary files. The tab is organized as a table with the following columns:

Column	Description
NAME	A field name defined during attribute creation or editing.
DATA	A field value.
SOURCE	The source of the field value input: workflow (automatic) or api (manual).

ID Documents

The ID Documents tab includes data for all documents processed via the Document Reader SDK, for example:

• Passports
• Driver’s licenses

Each document card includes:

• Results processed with the Document Reader SDK
• CREATED AT timestamp
• WORKFLOW name (only for automatic input)
• The related session link
• The related timeline link
• The More details spoiler button for extended info about the document data

Biometrics

The Biometrics tab contains all biometric photos, structured by the field content, such as:

• Selfie
• Fingerprints
• Retina

Each biometric entry includes:

• The current photo (the last uploaded for the field content category)
• The WORKFLOW name (only for automatic input)
• The related session link
• The related timeline link
• The More spoiler button to view previous photos

Screening

The Screening tab contains all potential matches between the verified person's profile data and entries found in compliance watchlists by internal and external screening providers, such as LexisNexis:

• Sanctions
• Politically exposed persons (PEP)
• Anti-money laundering (AML)
• Terrorism
• Adverse media
• Others

Each screening entry includes the following data:

Data	Description
Photo	The photo of the matched person from the watchlist (if available).
Title	A composite field of last, first, and middle names.
Provider Profile Reference	The reference to the external screening provider record for the specific watchlist match.
Tag	A color-coded visual tag that represents the reason for the watchlist match, such as sanctions, PEP, or adverse media.
REASON LISTED	The name of the screening provider’s watchlist where the match was found.
DATE OF BIRTH	The birth date of the matched person according to the watchlist.
ADDRESS	The address of the matched person according to the watchlist. Includes country and city.
LISTED ON	The date of listing the matched person in the watchlist.
GENDER	The gender of the matched person according to the watchlist.
CONFIDENCE	The estimated confidence level for the specific watchlist match, expressed as a percentage from 0 to 100.
Session link	The link to the related IDV Platform session.
SUMMARY	The brief textual explanation of why the matched person is included in the watchlist.
REFERENCES	The collection of references to external sources that mention the matched person.
CREATED AT	The timestamp of the specific match entry creation.
UPDATED AT	The timestamp of the specific match entry update.
UPDATED BY	The user account that updated the specific match entry.

Each entry must be assigned one of the following statuses:

Match Status	Description
SET STATUS	The default status automatically assigned to each screening entry. Expected to be manually updated by a compliance officer.
TRUE MATCH	The watchlist match has been confirmed as correct.
FALSE MATCH	The watchlist match has been determined to be incorrect.
INSUFFICIENT INFO	There is not enough information to make a clear decision about the watchlist match.

A compliance officer can resolve watchlist match entries either individually, using row-level controls, or in bulk by selecting the corresponding checkboxes.

Note

A detailed explanatory comment is required each time a compliance officer changes a watchlist match resolution status.

Attachments

The Attachments tab stores arbitrary files linked to the profile. Each attachment entry includes the following data:

Data	Description
NAME	The attachment file name.
COMMENT	An arbitrary comment string, added during the attachment upload.
CREATED BY	The workflow (automatic input) or the user account (manual input) that added the attachment.
CREATED AT	The timestamp when the attachment was added.
SIZE	The file size of the attachment.
Session link	The link to the related IDV Platform session.
Timeline link	The link to the related activity timeline.
Download link	The link for downloading the attached file.

Sessions

The Sessions tab displays all sessions that created, modified, or used the profile. Each session entry includes the following data:

Data	Description
Current status	The resolution status assigned to the session.
FLOW	The name of the workflow that was executed during the session and affected the profile.
CREATED	The session start date.
COMPLETED	The session end date (if completed).

Note

Deleted sessions are not displayed in this tab.

Geolocation

The Geolocation tab contains the complete log of detected IP and geographical locations and their changes for the opened profile. The tab also displays an interactive (zoomable and scrollable) world map with all detected location points.

Note

IP location and geolocation are recorded only when the Track Location parameter is enabled in the Profile Group Configuration.

Each entry in this tab contains the following data:

Data	Description
Timestamp	The timestamp of the IP or geolocation detection.
COUNTRY	The country of the detected IP or geolocation.
REGION	The region of the detected IP or geolocation.
CITY	The city of the detected IP or geolocation.
ISO ALPHA-2	The two-letter country code according to the ISO 3166-1 alpha-2 standard.
ISO ALPHA-3	The three-letter country code according to the ISO 3166-1 alpha-3 standard.
LONGITUDE	The longitude coordinate of the detected IP or geolocation.
LATITUDE	The latitude coordinate of the detected IP or geolocation.

Devices

The Devices tab contains the list of all devices that made changes to the selected profile. Each entry in the table contains the following data:

Data	Description
DEVICE ID	The unique alphanumeric string identifier of the mobile device or web browser.
PLATFORM	The specific platform (browser or mobile) used by the device. Available options: browser android iOS
DEVICE MODEL	The mobile device model or web browser version.
SESSIONS	An expandable section containing all sessions related to the current device or browser.

Note

Device info is recorded only when the Track Device parameter is enabled in the Profile Group Configuration.

Comments

The Comments tab contains the complete changelog of the profile statuses with comments, assigned to them. Each entry in the table contains the following data:

Data	Description
STATUS	The status assigned to the profile. Available status options: APPROVED REJECTED SUSPENDED
COMMENT	A non-empty string explanation of the profile status change.
LEFT BY	The user account that has changed the profile status and added a resolution comment.
CREATED AT	The timestamp of the profile status change.

Note

When a profile is open, you can change its status from any tab by using the controls pinned to the bottom of the screen. A resolution comment is mandatory in this case.

Timeline

The Timeline tab displays the detailed log of all profile-related events, including:

• Profile creation
• Attribute changes
• Data changes
• Workflow launches
• Status updates

Each event shows:

• The event type
• The input method (manual or automatic)
• The author (user or workflow)
• The timestamp
• Previous and new values (if applicable)
• The related session link

Populating Profiles and Groups

Profiles can be created and populated in two ways:

• Automatic input (workflow)—data is populated automatically through a workflow (records the workflow name and session link).
• Manual input—data is entered manually by an authorized user via UI (Platform portal) or API (records the account name used for data populating).

Automatic input (workflow)

Workflows can interact with profiles through the person action type. This action supports:

• Creating a profile in a group
• Searching profiles within a group using session data (biometric or textual)
• Updating profiles
• Extracting data from a profile into a session

Manual input

When manually creating a profile, an operator can:

• Fill in required fields defined for the group
• Upload and process an ID document via the Document Reader SDK
• Upload arbitrary documents processed outside the Document Reader SDK
• Upload photos
• Update a profile status
• Leave comments

Additional verifications

An operator with the required permissions can launch a new workflow session for the single selected profile by the Additional check button. To launch a workflow for the entire profile group use the Jobs menu (the Identity Refresh feature). In this case, profile data is passed into the session as input.