Manuals · Manager Manager
ROLE GUIDE

Read the business, not the queue

This guide is for management who use the Assentify Digital Experience Platform (DXP) to read the business without doing the day to day work. Learn to read the Dashboard, understand what every counter measures, tell in transit from dropped, and track risk from the RBA Score across the client book.

Dashboard · Funnel · Risk · Billing

About this guide

This manual is written for management who read the business, not the queue. You will learn to read the Dashboard, understand what every counter actually measures, spot when interactions are in transit versus dropped, and track the risk picture from the RBA Score across the client book.

You do not process applications here. You read the platform. The operators, the backend teams, and the compliance function do the daily work. Your job is to read the signal in the numbers, hold the operational rhythm, and steer capacity and risk.

Audience Head of Operations, COO, Head of Digital, Head of ComplianceVersion 2.1 · May 2026Classification Highly Confidential
You mostly touch three areasDashboard, Compliance Hub, and Settings (Billing Management). You read the platform; the operators and compliance teams do the daily work.
Related documentsAssentify Platform Tour, Assentify User Manual v3.6, and Assentify Compliance Hub v2 give the operator and compliance detail behind the numbers on your Dashboard.

Signing in and around the platform

Open the DXP URL from your administrator. You can only sign in with a work email that ends in your tenant domain.

  1. Open the DXP URL provided by your administrator.
  2. Enter your work email, then press Sign In.
  3. Enter your password, then press Login.
  4. If two factor authentication is on, enter the 6 digit code from your authenticator app.
TipYou can keep multiple tabs of the DXP open in the same browser. Signing in from a different browser ends your previous session.

Once signed in, the left side menu shows Dashboard, Clients, Compliance Hub, Logs, and Settings. As management you will mostly use Dashboard, Compliance Hub, and Settings (Billing Management).

The flow in one picture

A client interaction has a fixed lifecycle on the platform. Knowing it lets you read every Dashboard number correctly. The Dashboard shows live counts for each state per flow and across flows.

StateWhat it means
EngagementClient facing steps: Block Loader, Identification Document Capture, Face Image Acquisition, Assisted Data Entry, and similar.
In TransitThe interaction is in flight. Either the client is still walking through it, or it was submitted and is moving through Connector and Backend steps.
In Progress on a Backend BlockA human is reviewing the application.
DecidedAn Approve, Decline, or other configured decision was taken. The interaction leaves the queue.
DroppedThe client abandoned the flow before submitting. This is the number to watch for friction.
Why this mattersEvery counter on the Dashboard maps to one of these states. When a number looks wrong, ask which state it counts before you ask what broke.

How the modules fit together. The Dashboard is analytics. It feeds from three modules. Interactions holds the per-flow interaction lists, each with a configure icon that maps which fields show in an expanded interaction row. Clients is the register with KYC and AML status. Compliance Hub runs the screening and adjudication behind the risk numbers. To see how flows are built, use the Flow Builder guide. For roles and billing, use the Admin guide.

The Dashboard, card by card

Dashboard analytics
The Dashboard: KPI cards and insight panels, filtered by Day, Week, or Month.

What it is. Your at a glance view of the platform. Read it top to bottom: volume and speed at the top, then per flow insights, then the capture donuts, then the first and last engagement steps.

How the surface is split. The top row is tenant wide. The lower band is per selected flow. Pick a flow in Selected Flow to populate the lower band, then use the Day / Week / Month toggle to set the range. On the In Progress and Dropped donuts, hover to reveal an eye or view control. That control drills from a number into the underlying interaction records, so you can go from a count to the exact sessions behind it. The same records are also reachable from the Interactions module.

Top row: volumes and speed

CardWhat it measures
Total InteractionsWeekly bar chart of engagement sessions for the selected week, with a back and forward week pager.
Average Engagement Processing TimeTime clients spent inside the Engagement Block, shown as a line chart per block (Block 0, and so on) by weekday. A short value means clean flows. A long value usually means a friction step.
Average Backend Processing TimeServer-side backend time, shown as a line chart by weekday. Your operational SLA reading.
Read togetherA short Average Engagement Processing Time with a long Average Backend Processing Time means the client experience is clean but the backend queue is slow. Staff the backend, not the flow.

Engagement Insights

The lower band is per flow. Set the flow and the window before you read the counts.

  1. Pick the flow from the Selected Flow search box. Type in the Search flows... box, then choose the flow from the selector.
  2. Pick the window with the Day / Week / Month toggle.
  3. Read the status donuts below against that flow and window.

After a flow is selected you see three status donuts. These are the funnel at a glance for the chosen flow.

DonutMeaning
CompletedSessions that finished the whole journey.
In ProgressSessions still open. Hover for the eye control to drill into the list of in-progress sessions.
DroppedSessions abandoned before completion. This is your funnel leakage. Hover for the eye control to list the dropped sessions and inspect why each dropped.

The per-step ID and Face figures do not live here. They sit in the Performance Insights and Image Input Insights panels covered in the next section.

Diagnose a dropWhen Dropped climbs, work the cause in order. Open the flow, then read the ID and Face Performance Insights to see whether users failed capture or match. Next read Image Input Insights (Blurred Image, Unsupported ID, Authentication Failed) for the concrete reason. Finally use the eye drill-down on Dropped to list the exact sessions. This is your core throughput and conversion workflow.

Performance Insights and Image Input Insights

Two pairs of donuts. ID first, Face second. Each pair shows Performance Insights (how the step performed) and Image Input Insights (what the camera produced). Read the categories exactly as named below.

ID Performance

Success on first try, second try, third try, after three tries, No Auto Capture, Dropped, Error.

ID Image Input

Good Image, Authentication Failed, Blurred Image, Unsupported ID.

Face Performance

Matched on first try, multiple tries, No Match (Skipped), Dropped, Error.

Face Image Input

Good Image, Authentication Failed, Blurred Image.

Reading signalA spike in Authentication Failed under ID Image Input points to the camera or lighting on the client side. If Success After Three Tries dominates, the capture step is too strict. Talk to your Flow Manager.

Per-step timing

At the bottom of the Dashboard, a card for every engagement step in the flow shows its timing. Block Loader and Wrap Up appear, and so does every other step in between: ID capture, Face, Assisted Data Entry, and the rest. Each card shows Passed, Skipped, Error, plus Avg Time, 95 Pct High, and 95 Pct Low in seconds, so you can see exactly which step slows clients down.

FieldWhat it tells you
PassedInteractions that cleared the step.
SkippedInteractions that bypassed the step.
ErrorInteractions that failed at the step.
Avg TimeMean time on the step in seconds.
95 Pct High / 95 Pct LowThe slow and fast ends of the 95th percentile band, in seconds.
Watch thisWhen any step's 95 Pct High climbs, that step is becoming a friction point. If it is Block Loader specifically, your flow assets are too heavy.
What healthy looks likeThe confirmed per-step cards in the knowledge base are Block Loader and Wrap Up. Each shows Passed, Skipped, and Error plus Avg Time, 95 Pct High, and 95 Pct Low. In the sandbox, Flow 5 had Block Loader and Wrap Up each Passed 1 at roughly 0.15 to 0.24 seconds. That is the shape of a clean, fast step to compare against.

The funnel: in transit, dropped, decided

When you compare the same week to last week, watch three numbers together.

  1. Read Engagement starts, the Total Interactions including in transit.
  2. Read Dropped from Engagement Insights, the leak in the funnel.
  3. Read Completed (Decided) from Engagement Insights.
  4. Check the math below; a mismatch means an integration is silently failing.
  5. Open Logs to find the failing integration when the equation does not balance.
FUNNEL MATH

Engagement starts minus Dropped minus In Progress equals Decided

If the equation does not balance, you have an integration silently failing. The Logs section will show the failures.

Reading risk: RBA, Client Clear, matches

Two surfaces tell you the size of your risk book.

Where Compliance Hub > Client ClearWhere Side menu > Clients
  1. Open Compliance Hub, then Client Clear.
  2. Read the profile-type tabs at the top for counts per profile type.
  3. Read the RBA Score column to see how risky the book is at a glance.
  4. To size a tier, open Clients from the side menu.
  5. Filter by Risk Level (Low, Medium, High) for the live count at each tier.
RBA ScoreThe Risk Based Approach score is a numeric value from the Risk Based Approach engine. Sort the Client Clear RBA Score column descending to see your highest risk clients first.

The Clients table. Its columns come from the Client Profile mapping: Client ID, Email, Phone Number, Birth Date, Name, Time started, and Time Ended, plus KYC and AML status. Controls include Export, search, and Filters. So you can filter to a Risk Level, size that tier, and export the list for a review pack.

What the counts came fromThe risk book is the sum of adjudication decisions. When an analyst works a match, Confirm Match suspends the client. Confirm And Allow allows the client but sets Risk to High. Clear Match records no action as a false positive. See the Compliance guide actions on a match for how each decision is made.

Screening freshness and audit proof

Two questions the board asks most: how fresh is our screening, and can we prove the process to the regulator. Both are answered inside the Compliance Hub.

  1. Open Compliance Hub, then the Status sub-module.
  2. Read the last update per list; the default refresh is every 6 hours.
  3. For an audit trail, open Audit Hub and run the end of day export.
  4. For a flagged client, open Clients and export the AML Screening History.
Regulator readyThe Audit Hub export and the AML Screening History are timestamped, signed, and exportable. Together they are your proof of process.

How a match is generated. The hub screens each entity across many watchlists, for example UsOfacSdn, InterpolRedNotice, and UkOfsiTargets. It uses Agentic AI name variations to catch aliases and transliterations, so a misspelled or transliterated name still matches. Each match record carries a Score, Name, Alias list, and Country. Read these to judge screening quality, not just freshness.

Prove the process. The Compliance Hub Export Report offers Export To CSV and Export To Excel. In Logs, the Audit Type splits into User Activities and System Audit, with Created, Activity Type, User Name, and Message columns plus Export. That log answers the board's "did anyone bypass the process" question directly.

Operational rhythm

Run the platform on a steady cadence. This table sets who does what and when.

WhenWhatOwner
Every morningOpen Dashboard. Scan In Progress, Dropped, and AML matches.COO or Head of Ops
Weekly MondayCompare the past week to the prior week. Look for Performance Insight shifts.Head of Digital
Weekly FridayCompliance Hub Audit Hub export reviewed and signed off.Head of Compliance or MLRO
MonthlyBilling Management review. Quota burn versus quota allowance.Finance and COO
QuarterlyRoadmap discussion with Assentify Customer Success.COO and Assentify CSM
Recommended practiceA useful daily rhythm for the operations teams is simple. Triage Critical queues each morning, clear Standard mid-day, and run the Daily Onboarding Report at end of day, reconciling against core banking. Review webhook and notification failures in Logs weekly. Review the Confirm and Allow rate and the Critical-case rate monthly for signal drift.
Two-tier queue SLAsA common target set is a 10 to 30 minute SLA on Critical-priority cases in business hours. Standard cases target roughly 4 hours, and the compliance queue about 2 business hours. Teams work these off the Real Time view, not History.

Billing and Usage

Open Settings, then Billing Management. The top right card shows Your Usage with subscription type, Total Allowed, Total Consumed, Total Over, and a donut for percent consumed.

Where Settings > Billing Management
  1. Open Settings, then Billing Management.
  2. Read the Your Usage card: subscription type, Total Allowed, Total Consumed, Total Over.
  3. Read the donut for percent consumed to judge quota burn at a glance.
  4. Scroll to the invoice table for finance forecasting and renewal planning.

Monthly Subscription

Fixed monthly quota. Overage is charged per transaction.

Prepaid Transactions

A prepaid package. Processing stops when the package is exhausted.

The invoice table at the bottom lists these columns.

ColumnUse
Invoice IdReference for the billing period.
Month OfThe billed month.
Total (USD)Amount due in US dollars.
InteractionsVolume billed in that period.
StatusPaid or outstanding.
Prepaid runs out hardOn a Prepaid Transactions package, processing stops when the package is exhausted. Watch the donut and top up before Total Consumed reaches Total Allowed.

Common questions from the board

QuestionWhere to answer it
How long does our eKYC take?Average Backend Processing Time on the Dashboard.
How many clients are flagged for AML?Compliance Hub > Client Clear profile-type tabs show live counts per profile type.
How fresh is our screening?The Compliance Hub Status sub-module shows last update per list. Default is every six hours.
Are we paying for capacity we do not use?Yes if Total Consumed sits well below Total Allowed for several months.
Did anyone bypass the process?Logs section, filter by user and action type. Audit Hub for compliance specifically.
How big is our high risk book?Clients section, filter by Risk Level High. Or Client Clear, RBA Score column descending.

Scaling up

When the business grows, these are the levers and who pulls them.

GoalHow
Add a flowTalk to your Flow Manager. New flows can go live in days.
Add a languageArabic is built in. Other languages need Assentify Customer Success to enable.
Add a backend teamCreate a new Backend Block in the relevant flow.
Add a listYour Compliance team can add custom lists in minutes.
Add a profile typeSettings > System Configuration > Client Profile Types.
Add a transaction monitoring ruleSettings > RTRA Engine Configuration.

Roles and permissions

The DXP supports custom roles built from claims dragged into a role definition. The recommended starting roles for this audience are below. Your administrator can adjust the claims to match your operating model.

RoleRecommended accessTypical tasks
Head of Operations / COODashboard, Logs read, Billing read.Daily Dashboard scan, weekly review.
Head of DigitalDashboard, Flow Manager read, Theme Builder read.Owns flow performance, branding, and language pack expansion.
Head of ComplianceCompliance Hub (all four sub-modules), AML Management, Clients, Logs export.Owns the weekly compliance pack, regulator submissions, custom list policy, and RBA setup.

FAQ and support

QuestionAnswer
Is the Dashboard real time?Yes. New interactions and decisions roll in live.
Can I export to Power BI or Tableau?Yes, through the Developers section. The Solution Architect can wire the API.
How do we prove compliance to the regulator?End of day Audit Hub export, plus AML Screening History from the Clients section for any flagged client. Both are timestamped, signed, and exportable.
Where is our data stored?Settings, System Configuration. Data Persistence selects On Cloud or On Premise.
Can I get an SLA?Yes, through Enterprise tenancies. Talk to Customer Success.
Support and contactsFor platform issues, configuration help, or feature requests, contact your administrator first. They have visibility into your tenant configuration and will route platform level cases to Assentify Customer Success. Internal helpdesk: raise a ticket with your IT or Operations team. Assentify support email: support@assentify.com (filed through your administrator). Status updates: subscribe through your administrator's notifications setup.

Glossary

The terms behind the numbers on your Dashboard.

TermDefinition
AMLAnti Money Laundering.
Application CommandThe default step inside a Backend Block. Holds Automated Processing, Pre-Processing, decisions, and the Interactions table configuration.
Backend BlockWhere collected interaction data is reviewed and decisioned.
BIBusiness Intelligence.
ClientA natural person or business stored in the Clients section.
Compliance HubAML, sanctions, PEP, and watchlist module. Four parts: Workspace, Client Clear, Audit Hub, Status.
Connector BlockThe block that updates status, sends notifications, creates clients, and pushes data through webhooks.
DXPDigital Experience Platform. The Assentify product.
Digital EngagementA flow exposed to clients via a link, QR code, or SDK.
Engagement BlockThe client facing block with capture and signing steps.
FlowAn end to end journey built in the Flow Builder.
FunnelThe path a client takes from start to submitted application.
Inline Compliance HubThe AML screening panel that appears inside an expanded interaction row.
InteractionOne client submission travelling through a flow.
PEPPolitically Exposed Person.
RBA ScoreRisk Based Approach score. A numeric score from the Risk Based Approach engine.
RTRAReal Time Risk Assessment. The engine that monitors client transactions after onboarding.
Run rateProjected end of period cost or volume.
Screening ProfileA named configuration of which lists and which weighted algorithms run for a given context (Interactions, Client Clear, Workspace).
TenantAn Assentify client organization.
eKYCElectronic Know Your Customer.
NextSee the Admin guide to configure billing and roles, and the Compliance guide for the risk and screening controls behind the numbers.