ROLE GUIDE

Glossary & Reference

Every platform term in plain language, the map of all modules, the interaction lifecycle, and the guided demos. One reference merged from all five Assentify DXP manuals.

Module map · Master glossary · Watchlists · Roles

How to use this page

This is the shared reference for the Assentify Digital Experience Platform (DXP). It gathers the module map, the interaction lifecycle, the block model, the step catalogue, and one master glossary that merges the terms from the Management, Admin, Compliance Officer, Customer Service, and Flow Manager manuals.

The product is the Assentify Digital Experience Platform (DXP). Throughout, the person being onboarded is called the client. Proper nouns such as Customer Service and Customer Success keep their names. Read this page to settle a term quickly, then return to your own role manual for the full workflow.

Fast lookupUse the sidebar to jump to a section. The master glossary is alphabetical, so scan by first letter. Product terms are capitalized exactly as the platform shows them.

Every role signs in the same way. A work email that ends in your tenant domain is required.

Open the DXP URL your administrator provided.
Enter your work email, then press Sign In.
Enter your password, then press Login.
If two factor authentication is on, enter the 6 digit code from your authenticator app.

One sessionYou can keep several DXP tabs open in the same browser. Signing in from a different browser ends your previous session. Every new user is asked to set up 2FA on first sign in.

Module map

The left side menu changes with your role. This is the full surface an administrator sees.

Module	What it is for
Dashboard	Analytics: interactions, processing times, performance donuts, and drop-off insights.
Interactions	Every client session, its captured data, and its Status. The daily review queue.
Clients	The register of onboarded people and businesses, with KYC and AML status.
Documents	Document Template Builder. Upload .docx starter templates with merge tokens.
Flow Builder	Design onboarding journeys from Engagement, Connector, and Backend blocks.
Flow Manager	Publish flows and generate the Digital Engagement Link and Digital Engagement QR Code.
Compliance Hub	Screen names against sanctions and PEP lists, and adjudicate matches. Four sub-modules.
Communication	In-app chat with clients.
Developers	SDK keys, API, and Widget integration docs. The route to Power BI or Tableau.
Logs	Full audit trail of user and system activity, exportable and append only.
Settings	Users, roles, AML, Client Profile, Data Source, email, sessions, and more.
Transactions Hub	Real Time Risk Assessment on client transactions. Requires an RTRA subscription.

Interaction lifecycle

Every client interaction follows a fixed lifecycle. Knowing it lets you read every Dashboard number correctly.

State	Meaning
Engagement	Client-facing steps run: Block Loader, ID Capture, Face, Assisted Data Entry, and more.
In Transit	The interaction is in flight. The client is still walking through it, or it moves through Connector and Backend steps.
In Progress on a Backend Block	A human is reviewing the application in the Application Processing Command Center.
Decided	An Approve, Decline, or other configured decision was taken. The interaction leaves the queue.
Dropped	The client abandoned the flow before submitting. This is the number to watch for friction.

Funnel checkEngagement starts minus Dropped minus In Progress should equal Decided. If it does not, an integration is silently failing. The Logs section shows the failures.

The three blocks

Every flow is built from three block types. Chain them as many times as the journey needs.

Engagement Block

Client-facing. Holds capture, signing, questionnaire, address, document upload, chatbot, and slot booking steps. This is where the client experience lives.

Connector Block

Wires actions between client-facing work and operations. Status Change, Notification, Create or Update Client, and Webhook steps.

Backend Block

Operations and decisions

Holds the Application Processing Command Center, where your team reviews and decisions interactions. The default step is the Application Command, which carries Automated Processing, Pre-Processing, Decisions, and the Interactions table configuration.

Maker-Checker patternFor a four-eyes control on applications, build the pattern inside Flow Builder as Backend, then Connector, then Backend. For settings and flow changes, turn on Dual Maker / Checker Control in System Configuration.

Step reference

The Engagement Block offers these step types. Each is a screen the client sees.

Step	What it does
Block Loader	Preloads assets for a smooth start.
Informative Onboarding	Sets expectations: time, documents needed, complexity.
Terms and Conditions	Captures consent, including GDPR.
Service Selection	Lets the client pick a path.
Split	Branches based on a selection or value.
Facial Image Capture	AI face detection and liveness.
Identification Document Capture	AI capture, OCR, MRZ extraction, and document liveness.
Assisted Data Entry	A form pre-filled from earlier steps.
Questionnaire	Custom questions for KYC tiering or risk profile.
Address Capture	Captures and validates an address.
Document Capture	The client uploads supporting files.
Context Aware Signing	Issues a real-time document for digital signature.
Wrap Up	Final message before submit.

Connector Block steps push work outward: Status Change, Notification, Create / Update Client, and Webhook.

ID Capture togglesThe Identification Document Capture step exposes a deep panel: Title, Subtitle, Next Button, Logo upload, Skip Ability, Allow Passport, Country, Document Type, Front Only, Allow Mobile Based Capture, Set Mobile Capture as Default, Mobile Only Scanning, Show Result Page, Store Captured Document, Is Manual Capture, Document Liveness, and Disable Data Extraction.

KEY IDEA

One glossary, five manuals

The table below merges every glossary term from the Management, Admin, Compliance Officer, Customer Service, and Flow Manager manuals into one alphabetical reference. Where a term appeared in more than one manual, the fullest definition is kept.

Master glossary

Term	Meaning
ADE	Short for Assisted Data Entry, the form step pre-filled from earlier capture steps, for example OCR from the ID. Edits to auto-filled ADE fields are what raise the is_dirty / Modified flag.
Agentic AI Variations	AI-generated name aliases and spellings that widen the net for matching.
AML	Anti-Money Laundering. Screening names against sanctions and watch lists.
Application Command	The default step inside a Backend Block. Holds Automated Processing, Pre-Processing, Decisions, and the Interactions table configuration.
Application Processing Command Center	The screen inside a Backend Block step where flagged interactions are reviewed and decisioned.
Audit Hub	The Compliance Hub sub-module that scopes to compliance decisions, filtered by System User and Decision.
Automated Decisions	The rule builder inside Automated Processing that auto-decisions clean cases on arrival, so operators only see the rest.
Auto Classify on Value	A data point value that sets the risk level directly, overriding the score.
Backend Block	Server-side processing, enabled later in the chain, where collected interaction data is reviewed and decisioned. It renders as a pentagon on the canvas and defaults to the Application Command step feeding the Application Processing Command Center. See The three blocks and Flow Builder.
Base Currency	The 3 letter code the RTRA Engine normalizes transaction amounts to.
BI	Business Intelligence.
Block Loader	The first Engagement step. Preloads flow assets for a smooth start.
Claim	A specific access right combined with other claims into a role.
Client	A natural person or business stored in the Clients section. The person being onboarded.
Client Clear	The continuous screening queue in the Compliance Hub, showing every existing client the engine flagged since their last clear.
Client Profile	The Settings area that defines a client record. The tenant default profile type is Verified Person, alongside Person and Verified Business. It holds Configure Client Profile (the Map Profile Sources mapping that bridges captured data points to the Clients table), Risk Based Approach, AML Actions, Auto Risk Classification, Define Client Uniqueness, and the ongoing screening cadence. See RBA and RTRA and Settings map.
Compliance Hub	AML, sanctions, PEP, and watchlist module. Four parts: Workspace, Client Clear, Audit Hub, Status.
Connector Block	The block that updates status, sends notifications, creates clients, and pushes data through webhooks. It renders as a diamond on the canvas and is enabled only after an Engagement Block exists, carrying Status Change, Notification, Create / Update Client, and Webhook steps. See The three blocks.
Context Aware Signing	A step that issues a real-time generated document for digital signature, with options such as OTP and video consent.
Contributes to Risk Score	Setting where a data point adds a weight to the overall risk score.
Data Point	A single field a flow captures, such as Email or Nationality.
Data Source	A REST and SOAP integration to your own systems, set up in Settings. In the setup flow the type is API or SOAP, the auth is API Key or Basic Auth, and each endpoint is a Pull Data Request, Push Data Request, or JSON File. Always Test before Save. See Settings map.
Digital Engagement	A flow exposed to clients via a link, QR code, or SDK.
Digital Engagement Link	The canonical URL for a published flow, with a copy button in Flow Manager.
Digital Engagement QR Code	A printable code that opens the flow on a phone.
Double Metaphone	A sound based name matching algorithm, useful for spelling drift across languages. Part of Traditional Matching.
DPRC	Data Point for Risk Classification. A data point used to score risk.
Dual Maker / Checker Control	A two-approver workflow for settings and flow changes, turned on in System Configuration.
DXP	Digital Experience Platform. The Assentify product.
eKYC	Electronic Know Your Customer.
Engagement Block	The client-facing block with capture and signing steps.
FATF	Financial Action Task Force.
Flow	An end to end journey built in the Flow Builder.
Funnel	The path a client takes from start to submitted application.
Inline Compliance Hub	The AML screening panel that appears inside an expanded interaction row.
Interaction	One client submission travelling through a flow, with all its captured data.
Is_dirty flag	An internal signal that an application needs a human look, shown as the yellow Modified row color. It means a value that OCR, transliteration, or translation auto-populated into an Assisted Data Entry field was edited by the client after it was filled. It can be a bad extraction or transliteration, or a client altering a name or date of birth to push incorrect data through.
KYC	Know Your Customer. Identity verification and its expiry and renewal.
Limited Use Link	A share link that starts a fresh interaction each time it is used.
Maker-Checker	A four-eyes control where a second user approves an action.
Manual List	Your own internal watch list, checked alongside the standard lists.
Mapping Key	The key used to line up a captured data point with a target field. A Search Mapping Key box filters the Data Points Available For All Created Flows tree when mapping the Clients table or building a risk-scoring rule. See RBA and RTRA and Admin.
Match Percentage	The face to face score between the live selfie and the face extracted from the ID document.
Merge Tags	Tokens in the Email Template Builder that pull flow data points into an email body.
MLRO	Money Laundering Reporting Officer.
Modified	The yellow row color in the Status colors table. It is the same signal as the is_dirty flag: an edited auto-filled ADE value flagged for human review. See Status colors.
MRZ	Machine Readable Zone on a passport.
PEP	Politically Exposed Person. A separate screening focus.
Pre-Processing	Extra fields the operator must fill before a decision: Input Text, Attach File, Select Value.
RBA	Risk Based Approach. The model that gives each client a risk level.
RBA Score	Risk Based Approach score. A numeric score from the Risk Based Approach engine.
RTRA	Real Time Risk Assessment. The engine that monitors client transactions after onboarding.
RTRA Engine Configuration	The Settings area for the Real Time Risk Assessment engine, its life span, base currency, transaction structure, and rules.
Run rate	Projected end of period cost or volume.
SAR	Suspicious Activity Report.
Screening Profile	A named configuration of which lists and which weighted algorithms run for a given context (Interactions, Client Clear, Workspace).
Supporting eKYC flow	A follow-up flow started by a configured decision to collect additional information or documents from the client. The platform does not reset the original flow; it runs a short support flow and the new data joins the interaction.
SIEM	Security Information and Event Management.
SLA	Service Level Agreement. The time within which your team commits to process an interaction.
Smart Search	The match engine: Assentify Algorithms 60 percent plus Traditional 40 percent.
SMTP	Simple Mail Transfer Protocol.
Soundex	An English phonetic matching algorithm. Part of Traditional Matching.
Status	The state of a client or interaction, shown as a colored badge (for example active, AML flagged, KYC flagged, Modified).
Step	One screen in an Engagement Block, such as ID capture or a form.
Teller Mode	A Flow Builder canvas toggle, off by default, that switches a flow into agent-assisted or teller operation, where a staff member drives the engagement. It sits beside Allow Support, which is on by default and lets support agents assist during a live engagement. See Flow Builder.
Tenancy	An isolated, fully separate instance of the DXP for one tenant.
Tenant	An Assentify client organization.
Theme Builder	The branding surface for text, accent, and background colors, logo, and stepper style.
Token	A placeholder inside a document or email template, replaced by a data point at runtime.
Transaction Structure	The RTRA entity types (Sender, Receiver, Transaction) that rules evaluate, extendable with the plus icon.
Transliteration	Converting names between writing systems before matching.
Weak Alias	An alias entry in a source list that the source itself rates as lower confidence.
Webhook	An HTTP callback the platform fires when an event happens.
Workspace	The standalone Compliance Hub surface for ad hoc searches, bulk file based searches, and reportable sessions.

AML watchlists

The screening engine checks names against the standard watch lists below, plus any custom lists your tenant maintains.

List	Scope
US OFAC SDN and Non-SDN	United States Treasury sanctions, including FTM variants.
US Trade CSL	United States Consolidated Screening List.
UK OFSI Targets	United Kingdom financial sanctions targets.
OCC Enforcement Actions	United States banking enforcement actions.
Interpol Red and Yellow notices	Wanted persons and missing persons notices.
UN ISIS and Al Qaeda Sanctions List	United Nations terrorism sanctions.
UN 1988 Sanctions List	United Nations 1988 (Taliban) sanctions.
UN Security Council 1718, 1267 / 1989, Consolidated	Further United Nations sanctions regimes.
EU Consolidated Sanctions	European Union consolidated sanctions list.
Politically Exposed Persons (PEPs)	A separate screening focus for political exposure.
Lebanon: ISF Leb 24, SIC 18-26	Internal Security Forces and Banque du Liban Special Investigation Commission lists.
Custom lists	Lists maintained by the tenant (Demo in the sandbox).

FreshnessInternational lists refresh every six hours from each source. The Compliance Hub Status sub-module shows the last update per list.

Screening and matching

Where Settings > AML Management > Screening Profile

The Screening Profile defines how the engine searches every time you press search in Workspace, Client Clear, or inside an inline review. The score splits across two matching families.

Traditional 40%

Traditional Matching Algorithms

Forty percent of the score. Each algorithm has its own slider that sums to 100 percent inside the 40 percent envelope. Includes Double Metaphone (sound based name matching, useful for spelling drift across languages) and Soundex (English phonetic matching).

AI Matching 60%

AI Matching

The remaining 60 percent. Handles cultural and geographic variants, common typos, and transliteration between writing systems.

To tune the Screening Profile:

Open Settings and then AML Management.
Set the top level toggles Perform Background Check On All Clients and Flag Client Application On AML Match.
Pick a profile from the Profile Name picker, for example Default.
In Apply On, choose the surfaces that use this profile: Interactions, Client Clear, Workspace.
Adjust the Traditional Matching Algorithms sliders inside the 40 percent envelope.
Confirm the AI Matching weight holds the remaining 60 percent.
Press Save.

Adjudicate a match with one of three actions:

Action	Meaning	Effect on client
Confirm Match	The list record is the same person or entity.	The client is suspended. The interaction cannot move forward.
Confirm and Allow	Same person, and you allow the interaction anyway.	Risk is set to High and the interaction proceeds.
Clear Match	Different person or entity, a false positive.	No action. The match is dismissed, and the interaction can proceed once every red list is cleared.

To run an ad hoc search in the Compliance Hub Workspace:

Open Compliance Hub and then Workspace.
Set Entity Type to person or business.
Type the name in Search. Press the plus to add more names.
Set filters: Lists, Country, Address, Date of Birth, Industry, Document Number, From / To dates.
Set Apply Transliteration To for Arabic or Latin script handling.
Set Compliance Search For to AML or Full (adds Social Search and Assentify Client Search).
Turn on Show Only Hits to hide cleared lists, and Advanced Search for a wider net.
Press Export Report to download the session for audit and regulator submission.

To work a flagged client in Client Clear:

Open Compliance Hub and then Client Clear.
Pick the tab for the affected profile type: Person, Verified Person, or Verified Business.
Work the most recently flagged clients first.
Open the client. The biometric panel and Inline Compliance Hub appear inside the profile.
Press View More on each match to read the full record.
Choose Confirm Match, Confirm and Allow, or Clear Match, and add a note for the audit trail.

RBA and RTRA

Where Settings > Client Profile & Settings > RTRA Engine Configuration

The Risk Based Approach gives each client a numeric RBA Score. Real Time Risk Assessment watches live transactions after onboarding.

Real Time vs HistoryReal Time means RTRA watches live transactions after onboarding through the Transactions Hub, gated by an RTRA subscription. The historical review surfaces, Interactions and Client Clear, act on already-captured data. Use Real Time to catch a transaction as it happens, and the history surfaces to review what was already captured.

To configure the Risk Based Approach:

Open Settings and then Client Profile.
Pick the profile tab: Verified Person or Verified Business.
Turn on the Risk Based Approach toggle.
Add tiers with the plus icon. Defaults are Low, Medium, and High.
Drag the sliders on the 0 to 10 strip. Sandbox defaults are 3.00 between Low and Medium, and 8.00 between Medium and High, so Low is 0 to 3.00, Medium is 3.00 to 8.00, and High is 8.00 to 10.
Save. The RBA Score column in Client Clear and the Clients section now colors and ranks clients by these tiers.

To define an RTRA rule:

Open Settings and then RTRA Engine Configuration.
Set RTRA Engine Life Span in days, Base Currency, and the Transaction Structure (Sender, Receiver, Transaction).
Set Rule Name and Rule Span in days.
If the rule is short lived, turn on Temporary Rule.
Build the Rule Structure: pick the Entity, Attribute, Operator, and Value. Add conditions with the plus icon.
Pick the Action that fires when the rule matches.
Write the Output Message the system attaches to the action.
Press Add. The rule appears in the Defined Rules table with Status, Type, and Remaining lifespan.

Realtime AML tie-inTurn on Include Realtime AML Screening Check to tie RTRA decisions to a live AML check on the parties involved.

Status colors

Row and profile colors carry meaning in the Application Processing Command Center and the Clients section.

Color	Flag	Meaning
Red	KYC / IDV	A KYC concern, most often an expired or about to expire ID, a low face match, an ID authenticity review, or detected tampering.
Orange	AML	The AML screening engine found at least one possible match against a watch list.
Yellow	Modified	An is_dirty flag fired. The client edited a value that OCR, transliteration, or translation auto-filled into an Assisted Data Entry field.

Tampering signalsThe yellow Modified flag can also mean a face replace (a live face overlaid on the document) or a data replace (a fake card placed over the real card). The platform protects against both and surfaces the case for a human look.

Settings map

Settings on the side menu opens a grid of cards. This is where every tenant control lives.

Card	What it controls
User Management	Roles built from claims, and users.
Email Setup	The tenant SMTP server so notifications come from your domain.
System Configuration	Data Persistence, Time Zone, Theme Settings, profile types, payment gateway, Dual Maker / Checker Control.
Billing Management	Subscription, quota, Total Allowed, Total Consumed, and invoices.
Client Profile	Verified Person and Verified Business setup, uniqueness, screening cadence, and RBA.
AML Management	Screening Profiles, custom lists, and the two top level AML toggles.
Data Source	REST and SOAP integrations with endpoints and XSLT transforms.
Session Management	Session length and the password policy.
RTRA Engine Configuration	Real Time Risk Assessment engine and rules.

To add a Data Source and its endpoints:

Open Settings and then Data Source.
Press the plus icon and name the source.
Pick the type: API or SOAP.
Choose the auth: API Key or Basic Auth.
Fill in the URL and credentials. Press Test, then Save.
Open the source and add endpoints: Pull Data Request, Push Data Request, or JSON File.
Add headers, body, and an XSLT transformation for inbound payloads if needed.

Test firstAlways Test before Save. Runtime webhook failures are harder to debug than design time auth errors.

To configure the tenant SMTP in Email Setup:

Open Settings and then Email Setup.
Enter SMTP Mail Server, User Name, SMTP Port Number, password, and Sender Email.
Toggle SSL Required and Authentication Required as needed.
Press Save. All future flow notifications use this SMTP.

Roles and permissions

The DXP supports custom roles built from claims dragged into a role definition. The recommended starting roles across all five manuals are listed below. Your administrator can adjust the claims to match your operating model.

Role	Recommended access	Typical tasks
Head of Operations / COO	Dashboard, Logs read, Billing read.	Daily Dashboard scan, weekly review.
Head of Digital	Dashboard, Flow Manager read, Theme Builder read.	Owns flow performance, branding, language pack expansion.
Head of Compliance	Compliance Hub (all four sub-modules), AML Management, RTRA Engine Configuration, RBA setup, Clients, Logs export.	Owns the weekly compliance pack, regulator submissions, custom list policy, thresholds.
Compliance Officer	Compliance Hub (all four sub-modules), Clients read and edit AML status, Logs export.	Review inline matches, run Workspace sessions, action Client Clear, sign off RTRA flags.
MLRO	All Head of Compliance rights, plus Reports export and Settings read.	Sign off SARs, regulator submissions, audit responses.
Customer Service Operator	Interactions read and edit, Clients read.	Process the daily queue, reply to clients.
Customer Service Manager	All Operator rights, plus Export, Customize View, Reassign.	Run the queue, monitor SLA, handle escalations.
Flow Designer	Flow Builder, Flow Manager, Documents, Theme Builder.	Build and edit flows, manage templates and theme.
Business Administrator	All Flow Designer rights, plus Data Source and most Settings.	Approve flow changes, manage integrations.
Solution Architect	All Business Administrator rights, plus Developers.	Wire SDKs, APIs, and end to end integrations.
Tenant Administrator	Full claims across User Management, Settings, Logs.	Owns users, roles, settings, integrations, security.
IT Lead	User Management, Email Setup, Data Source, Developers, Logs.	Owns integrations, SMTP, API keys.
Platform Owner	Read across everything, write on Settings and Email Setup.	Owns the vendor relationship and roadmap with Assentify.

To build or adjust a role:

Open Settings and then User Management.
Press Manage Roles.
Press the plus to create a role, or pick an existing role to edit.
Set the role name in the Role Name field.
Drag components or specific claims from the library into the role.
Press Save.

Rename safelyClaims travel with the role record, not the name. You can rename a role without breaking access, and the rename is captured in the audit.

Operational rhythm

The Management manual sets a shared cadence for reading the business. Use it as the baseline calendar.

When	What	Owner
Every morning	Open the Dashboard. Scan In Progress, Dropped, and AML matches.	COO or Head of Operations
Weekly Monday	Compare the past week to the prior week. Look for Performance Insight shifts.	Head of Digital
Weekly Friday	Review and sign off the Compliance Hub Audit Hub export.	Head of Compliance or MLRO
Monthly	Billing Management review. Quota burn versus quota allowance.	Finance and COO
Quarterly	Roadmap discussion with Assentify Customer Success. User and role review.	COO and Assentify CSM
Yearly	Rotate API keys and webhook secrets.	IT Lead

Guided demos

Click-by-click walkthroughs with screenshots. Each demo links to the matching narrated video inside its guide.

Demo Flow: Customer eKYC

A complete eKYC sample flow, and an example of what you can build with Assentify in under an hour.

Open demo →

Run and adjudicate a screening

Screen a name, read the matches, and decide Confirm, Allow, or Clear.

Open demo →

Set up the Risk Based Approach

Configure risk levels and both scoring methods for compliance.

Open demo →

FAQ

Is the Dashboard real time?

Yes. New interactions and decisions roll in live.

What is the difference between AML in Workspace and Client Clear?

Workspace is a manual search you control. Client Clear is the continuous engine showing which existing clients matched on the last refresh. Both use the same Screening Profile.

How do I get more information versus declining?

When the client can supply what is missing, such as a clearer document or proof of address, a configured decision starts a supporting eKYC flow that collects it. Decline when the application is clearly not acceptable, such as confirmed fraud or tampering. The decisions available to you are set by your Flow Builder.

Why is a row yellow, red, or orange?

Yellow is Modified (an is_dirty flag). Red is a KYC or identity concern. Orange is an AML possible match. See the Status colors table above.

The decision buttons are greyed out. Why?

A required pre-processing field is empty, or an AML match is not cleared. Fill every required field and clear or confirm every red list in the Inline Compliance Hub.

Can I export to Power BI or Tableau?

Yes, through the Developers section. The Solution Architect can wire the API.

Can I undo a decision?

Not from an operator account. Contact your manager. An administrator can pull the interaction back into the queue in special cases.

My change does not show up on the phone.

Press Clear Cache in Flow Manager. Assets are cached aggressively.

A webhook keeps failing.

Open Logs and filter by webhook. The response body and HTTP status are recorded. Use Test on the Data Source endpoint to reproduce.

How do I prove compliance to the regulator?

Use the end of day Audit Hub export, plus the AML Screening History from the Clients section for any flagged client. Both are timestamped, signed, and exportable.