Manuals · Administrator Administrator
Role Guide

Administrator guide

Keep the tenant healthy and configured for your organization. This guide covers the three big areas an administrator owns on the Digital Experience Platform (DXP): settings, audits, and Client Profile setup, plus users, roles, AML, and integrations.

Tenant Administrator · IT Lead · Platform Owner

About this manual

This manual is written for the people who keep the Assentify DXP healthy and configured for their organization. It covers three big areas: settings, audits, and Client Profile setup. Use it alongside the Assentify Platform Tour, the Assentify User Manual, and the Compliance Hub guide.

Audience Tenant Administrator, IT Lead, Platform OwnerVersion 2.1 · May 2026

Signing in and around the platform

What it is. The way you and every user reach the tenant. Sign in uses a work email that ends in your tenant domain, then an optional two factor code.

  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 the full surface: Dashboard, Interactions, Clients, Documents, Flow Builder, Flow Manager, Compliance Hub, Communication, Developers, Logs, Settings. As an administrator you have access to all of them.

The Settings landing page

Where Settings

What it is. Settings on the side menu opens a grid of cards. Each card is one area of tenant configuration. Every card in the table below is documented in this guide.

CardWhat it configures
User ManagementRoles and users.
Email SetupThe tenant SMTP server.
System ConfigurationData persistence, time zone, theme, profile types, payment gateway.
Billing ManagementSubscription, quota, invoices.
Client ProfileVerified Person and Verified Business profile configurations.
AML ManagementScreening Profiles, custom lists, top level toggles.
Data SourceREST, Soap, and Data Set connections, plus Webhook and government integrations.
Session ManagementSession length, idle timeout, and password policy.
RTRA Engine ConfigurationThe Real Time Transaction Risk Assessment engine and rules. It requires an active RTRA subscription and setup, so it may not be present on every tenant.
RF1 BDL CircularToggles Turn on RF1 BDL Circular Reporting for regulatory reporting to the Banque du Liban RF1 circular, and reveals reporting config when on.

Audits and logs

Where Logs

What it is. Logs on the side menu shows the platform wide audit. Every row is one recorded event across the tenant.

ColumnMeaning
CreatedThe timestamp of the event, in the tenant time zone.
Activity TypeThe kind of event, for example a setting change or a webhook call.
User NameThe user or system actor that triggered the event.
MessageA short summary of what happened.
  1. Open Logs from the side menu.
  2. Press the + icon on a row to expand it for the full payload.
  3. Filter the table to the rows you need.
  4. Press Export at the top right to download the filtered view.
Compliance auditsFor compliance specific audits, also use Compliance Hub > Audit Hub. It scopes to compliance decisions and exposes filters for System User and Decision.
Recommended practiceRetain a full evidence pack for every interaction. Keep the document-capture audit video, the live-face image stream, and the eIDAS-signed KYC summary PDF. Also keep an activity trail that logs who did what, when, and why for every view, clear, confirm, and decision.

User Management

Where Settings > User Management

What it is. Roles are built from claims. A claim is the right to view or act on one part of the platform. Drag a whole module or specific claims into a role, then assign the role to a user.

Manage Roles, step by step

  1. Open Settings > User Management.
  2. Press Manage Roles.
  3. Press the + to create a new role, or pick a role to edit.
  4. Set the Role Name.
  5. Drag components or specific claims from the library into the role.
  6. Press Save.

Block Access: how custom flows become runnable

Granting a role's Associate Permissions is not enough to open a custom flow. Manage Roles has a Block Access section that lists every flow by UUID as checkboxes. The Administrator role alone carries every permission except per flow block access.

  1. Open Manage Roles and pick a non-admin role, for example ALL ROLES.
  2. Scroll past the Associate Permissions cards to the Block Access section.
  3. Check the flow you want to grant, then press Save.
  4. Open the user and associate that role alongside Administrator.
New flows need a fresh tickA newly built flow adds a new Block Access checkbox. Tick that checkbox and save before the flow appears in Flow Manager.

Adding a user

  1. Enter First Name and Last Name.
  2. Enter the user's Email.
  3. Enter the Date of Birth. This field is required.
  4. Assign one or more Roles.
  5. Optionally add a Picture, Phone Number, and Department.
  6. Press Save to create the user.
Welcome emailThe new user receives a welcome email with a default password. They must change it on first sign in.
Identity runs on a Financial-Grade SSO serverUser and client identity run on a well-known Financial-Grade Single Sign-On server, with full FATF-aligned lifecycle management, face-based authentication, and MFA.

Roles and permissions

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

RoleRecommended accessTypical tasks
Tenant AdministratorFull claims across User Management, Settings, Logs.Owns users, roles, settings, integrations, security.
IT LeadUser Management, Email Setup, Data Source, Developers, Logs.Owns integrations, SMTP, API keys.
Platform OwnerRead across everything, write on Settings and Email Setup.Owns the vendor relationship and roadmap with Assentify.

Client Profile setup

Where Settings > Client Profile

What it is. The configuration behind each client's profile page. Two tabs sit at the top: Verified Person and Verified Business. Each profile type is configured separately.

  1. Open Settings > Client Profile.
  2. Choose the Verified Person or Verified Business tab.
  3. Set Client Title and Client Subtitle, the header on the client profile page.
  4. Set the Show toggles for KYC Documents, Captured Documents, Signed Documents, and Interactions Table.
  5. Set Run AML Screening Every X Days. The default is 3.
  6. Set Alert Time Before KYC Expiry in days. The default is 30.
  7. Set Alert Time Before KYC Renewal in days. The default is 1000.
  8. Use Import to bulk import client profiles from a CSV.
  9. Use Configure Client Profile to add custom data points and map them to flow outputs.
  10. Press Save.

Configure Client Profile: mapping flow data onto the record

Configure Client Profile opens Map Profile Sources, the Clients Table Configuration. It maps Data Points Available For All Created Flows onto the client record fields Client Profile Data 1..N. Each mapped field shows its flow source, for example Demo flow > Engagement > Assisted Data Entry > Email. Each field also has two toggles, Is Displayed On Table and Is Filterable. Client Profile Data 1 is Client ID and is locked. This is the bridge between what a flow captures and what appears and is filterable in the Clients module.

More than display togglesThe Client Profile page also hosts two rule builders. AML Actions defines what happens on an AML match, such as block, flag, or review. Auto Risk Classification sets a client's risk level automatically from an AML outcome. Each opens its own rule builder from the plus at the section's left edge. See Compliance guide for the risk model.
FieldDefaultWhat it drives
Run AML Screening Every X Days3Rescreen cadence. The usable interval depends on client count. Contact Assentify for a different interval or an upgrade.
Alert Time Before KYC Expiry30Drives the yellow KYC flag.
Alert Time Before KYC Renewal1000Drives the renewal sweep.
Interval depends on client countThe usable rescreen interval depends on your client count. Contact Assentify for a different interval or an upgrade before you change it in production.
Recommended practiceA common KYC renewal baseline is 3 years, aligned to FATF guidance. Documents with no expiry date inherit that 3-year renewal date, and the Clients screen flags a client as the renewal window approaches.

Define Client Uniqueness

What it is. The rule set that stops duplicate clients. It sits on the right side of the Client Profile page. The platform refuses to create duplicate clients across these dimensions.

  1. Confirm Use biometric face encoding for uniqueness is on. It is on by default.
  2. Add additional unique elements with the Search Column Name field, for example phone number or national ID.
  3. Press Save to apply the uniqueness rules.

The Assign Client Profile Elements that must be Unique multi-select complements the biometric face encoding toggle. The elements you can mark unique are Client ID, Email, Phone Number, Birth Date, Name, Profile Picture, Time started, and Time Ended.

How uniqueness is keyedClient uniqueness can be keyed on a durable OTP-validated phone number, or on biometric (face) plus biographic data defined here. The mapped profile picture, the stored live face, drives cross-client biometric de-duplication.

Risk Based Approach

What it is. Risk Based Approach is on by default. Risk Levels show as colored badges (Low, Medium, High). The 0 to 10 strip below the badges shows the thresholds with sliders. The RBA Score column on Client Clear uses these tiers.

  1. Add tiers with the + icon next to the risk badges.
  2. Drag the slider to set the threshold between Low and Medium. The sandbox default is 3.00.
  3. Drag the slider to set the threshold between Medium and High. The sandbox default is 8.00.
  4. Press Save.
ThresholdSandbox default
Between Low and Medium3.00
Between Medium and High8.00

Configure Risk Profile

Configure Risk Profile opens Clients Risk Scoring Configuration. You pick data points from Data Points Available For All Created Flows and build a Clients Risk Score Structure by assigning Weights to rules, with a running Total Weights.

Each rule sets a Risk Behaviour. Contributes to Risk Score adds the rule's weight, and the summed total maps to a Low, Medium, or High band. Auto Classify on Value sets the risk level directly and overrides the score, for hard rules like a sanctioned country. Values Classification Mapping maps each possible value to a weight or a target level. See the Compliance guide for the full walkthrough.

AML Management

Where Settings > AML Management

What it is. The tenant wide AML controls, custom lists, and the Screening Profile that decides which algorithms run and how they are weighted.

  1. Set Perform Background Check On All Clients at the top of the page.
  2. Set Flag Client Application On AML Match.
  3. Use Add New List to add a custom list. Each custom list shows as a pill with a + icon.
  4. Tune the Screening Profile weights described below.
  5. Press Save.
Traditional Matching Algorithms

The 40 percent bucket splits across four matchers, each with its own percentage: Leverage Double Metaphone, Leverage Soundex, Leverage Skeleton, and Leverage Phonetics. These catch phonetic and spelling drift.

Advanced Features

The AI group carries Perform Agentic AI Variations, Apply Transliteration, and Fuzzy Matching. These catch cultural and geographic name variants, typos, and script differences.

Smart Search Scoring BreakdownTwo controls tune the result set. Max AML Smart Search Result truncates the result list when the count is exceeded. Min AML Smart Search Score is a threshold where higher values reduce false positives. Together the traditional matchers and the Advanced Features feed one combined score, so name variants are caught alongside phonetic spelling drift.

System Configuration

Where Settings > System Configuration
System Configuration
System Configuration: general settings, theme, client profile types, and payment gateway.
SettingWhat it controls
Data PersistenceOn Cloud or On Premise. On Premise requires a proxy address and a deployment at your data center.
Support EmailThe address that receives platform support cases.
Billing EmailThe address that receives monthly invoices.
Time ZoneThe tenant time zone used everywhere times are displayed.
Dual Maker / Checker ControlTwo approver workflow for settings and flow changes.
Theme SettingsUpload Primary Logo for the platform theme.
Client Profile TypesPerson, Verified Person, Verified Business toggles.
Payment GatewayThe tenant payment gateway credentials: Merchant ID, Key, and Shared Secret Key.
  1. Choose Data Persistence: On Cloud, or On Premise with a proxy address.
  2. Set Support Email and Billing Email.
  3. Set the Time Zone for the tenant.
  4. Turn on Dual Maker / Checker Control if you want two approver control on settings and flow changes.
  5. In Theme Settings, use Upload Primary Logo to set your brand logo.
  6. Set the Client Profile Types toggles for Person, Verified Person, and Verified Business.
  7. In Payment Gateway, enter the Merchant ID, Key, and Shared Secret Key for the tenant payment gateway.
  8. Press Save.
Daily maker / checkerDual Maker / Checker Control here governs settings and flow changes. For daily maker / checker on applications, build the pattern inside Flow Builder (Backend > Connector > Backend).
Signing and the tenant certificateDocuments signed through Context Aware Signing are eIDAS-compliant, applied in real time on a runtime-generated PDF. They are sealed with the tenant certificate's public-key cryptography. Consent is captured by tick or by voice.

Email Setup

Where Settings > Email Setup

What it is. The SMTP server the tenant uses for all flow notifications. Once set, emails appear to come from your domain, not Assentify.

  1. Enter the SMTP Mail Server.
  2. Enter the User Name.
  3. Enter the SMTP Port Number.
  4. Enter the account password.
  5. Enter the Sender Email.
  6. Toggle SSL Required and Authentication Required as needed.
  7. Press Save.

Session Management

Where Settings > Session Management

What it is. The session length and password policy for every user in the tenant.

  1. Set the Session length in minutes. The default is 15.
  2. Set the Idle timeout (minutes) to log a user out after inactivity, separate from total session length.
  3. Set the Password Policy toggles: Require Digit, Require Lowercase, Require Uppercase, and Require Non-Alphanumeric.
  4. Set Required length. The default is 9.
  5. Set Required Unique Chars. The default is 1.
  6. Press Save.
SettingDefault
Session length (minutes)15
Idle timeout (minutes)Inactivity logout, set separately from session length.
Required length9
Required Unique Chars1

Data Source

Where Settings > Data Source

What it is. Connections to your own systems. Each data source is a card with a pencil to edit and a + icon to add. Each source holds endpoints (Pull Data Request, Push Data Request, JSON File) with headers, body, and optional XSLT transformation. The card level source types are Data Source, Webhook, and Integration Government.

Where data sources are consumedConfigured data sources are the platform data relay. They feed Service Selection (Source Type = Data Source), Payment (Source of Payment Data = Data Source), RBA scoring, Client Profile mapping, and Connector block lookups. See the Builder guide for how flows reference them.
  1. Press the + icon to add a source.
  2. Enter the source name.
  3. Choose the Data Source Type: REST, Soap, or Data Set.
  4. Choose the auth: API Key or Basic Auth.
  5. Enter the URL and credentials.
  6. Press Test.
  7. Press Save.
TipAlways Test before Save. Runtime webhook failures are harder to debug than design time auth errors.
Failed webhooks are not lostOn a webhook failure (timeout, 5xx, or network error) the platform retries with exponential backoff. It dead-letters the event to Operations and Logs. It holds the interaction at Approve until the downstream system acknowledges, so no approval is silently lost.
Recommended practiceAuthenticate a Data Source with an API Key as a baseline. For banking-grade integrations, use mutual TLS plus a rotating bearer token pulled from a secrets vault.

Billing Management

Where Settings > Billing Management

What it is. Your subscription usage and invoice history. The top shows an Interactions chart by Week Of, and a Your Usage card with Total Allowed, Total Consumed, Total Over, and a percent donut. The bottom is the invoice table.

Invoice columnMeaning
Invoice IdThe invoice reference.
Month OfThe billing month.
TotalAmount due in USD.
InteractionsInteractions counted in the period.
StatusThe payment status of the invoice.

Security and Sessions

What it is. The security controls that protect every account in the tenant.

ControlHow it works
Two factor authenticationSet at tenant level. The platform prompts every new user to set up 2FA on first sign in.
Session policyOne active session per user across browsers. Signing in elsewhere ends the first session.
Password policyConfigured under Session Management.
Account lockoutAutomatic after a configured number of failed attempts.
AuditEvery change to security settings goes to the Logs section.

Tenant Hygiene

Keep the tenant clean with a regular cadence of reviews.

CadenceTask
QuarterlyUser review. Audit the user list and deactivate anyone who has left the team.
QuarterlyRole review. Claims drift over time.
MonthlyList refresh check. The Compliance Hub Status sub-module shows last update per list.
MonthlyBilling review. Track quota burn.
YearlyKey rotation. Rotate API keys and webhook secrets annually.
Support and contacts

Route platform issues through your administrator

For platform issues, configuration help, or feature requests, contact your administrator first. The administrator has visibility into your tenant configuration and routes platform level cases to Assentify Customer Success. Raise internal tickets with your IT or Operations team. The Assentify support email is support@assentify.com, filed through your administrator.

FAQ and troubleshooting

A user cannot sign in.

Check the user is active. Check the email ends in the tenant domain. Reset the password. If 2FA was lost with a phone, clear MFA so the user re-enrolls.

Can I retrieve an interaction that was decided in error?

Open the interaction in History view. If your role has Retrieve rights, press Retrieve. Otherwise raise a ticket with Customer Success.

Can I rename a role without breaking access?

Yes. Claims travel with the role record, not the name. Renames are captured in the audit.

A webhook is timing out.

Open Logs, filter by webhook. The response body and HTTP status are recorded.

How do I move from cloud to on premise data persistence?

Schedule a deployment with Customer Success. Plan downtime for cutover.

Is the audit tamper evident?

Yes. The log is append only at the platform layer. For higher assurance, export regularly to your SIEM.

Can I bulk import users from a spreadsheet?

Yes for Enterprise tenants. Ask Customer Success for the bulk import template.

How do I add a new email domain to the tenancy?

Raise a request with Customer Success. Domain allow lists are tenant level and not self serve.

NextSee the Compliance guide for AML and risk decisioning, and the Builder guide for how flows use these integrations.