Skip to content
FlowSentry Help Centre
Browse Getting started

Getting started

All topics

Getting started

Your first day, by role

Quick paths for analysts, MLROs, KYC and onboarding staff, risk managers, administrators, auditors and executives.

Everyone
On this page
  1. Analyst
  2. Senior analyst
  3. MLRO or Deputy MLRO
  4. KYC reviewer
  5. Relationship manager
  6. Senior approver
  7. Risk manager
  8. Administrator
  9. Integration engineer
  10. Auditor, QA reviewer or executive
  11. Related

This page gives each role a short, practical route through its first day. Before you start, make sure you can sign in and have an authenticator app or passkey set up — see Sign in, set up MFA and understand step-up. Not sure which role you have? Open the user menu (your name, top right): your roles are listed under your name.

Analyst

  1. Open Alerts & cases (/alerts). Start in My work; if it is empty, select Claim next to take the highest-priority unassigned alert.
  2. Open an alert. Read why the rule fired: the thresholds against the actual values and the transactions that tripped it. Try Summarise with AI for a plain-language reading.
  3. Check the customer's profile for context, then either close the alert with an outcome, a reason code and a rationale, or select it on the queue and Open case.
  4. In a case, use Investigate with AI for a draft memo, review the tabs, add notes and, if you suspect laundering, record suspicion on Suspicion & STR.
  5. Look at Hits (/screening) if your team also works screening.

Read next: Investigate an alert end to end.

Senior analyst

Everything an analyst does, plus:

  1. Check My approvals (/approvals/inbox) and the bell for screening matches and clears waiting for your confirmation.
  2. Work QA review (/qa): pass sampled closures or return weak ones for rework.
  3. Use Bulk close on the alert queue for scenarios your alert-work policy allows.

Read next: Analyst and senior analyst.

MLRO or Deputy MLRO

  1. Open MLRO decisions (/approvals). Each recorded suspicion shows its narrative, grounds, transactions and evidence, and the time left on the suspicion clock.
  2. Use Check goAML readiness before you decide, then File STR (with step-up), Return it to the investigator, or Do not file with grounds.
  3. Check My approvals for rules, KYC changes, risk overrides and other items waiting for you.
  4. Review Reporting (/reporting) for filings awaiting hand-off to the FIU portal, and the Executive overview dashboard.

Read next: Draft and file an STR and the MLRO guide.

KYC reviewer

  1. Open Customers (/customers). Filter by Incomplete KYC, IDs expiring or Reviews overdue using the tiles at the top.
  2. Open a customer and propose corrections with Edit KYC details; another person approves them.
  3. If onboarding is switched on for your institution, review applications in Applications (/onboarding) and the IDV review queue (/onboarding/reviews).
  4. Work enhanced due diligence checklists in the EDD workbench (/risk/edd).

Read next: KYC and onboarding guide.

Relationship manager

  1. Open Applications (/onboarding) and Start an application for a new customer.
  2. Answer any Information requests (/requests) from the compliance team.
  3. Look customers up on Customers and propose KYC updates when details change.

Read next: Onboard a corporate customer.

Senior approver

  1. Check My approvals and the bell for onboarding applications, EDD cases and KYC changes waiting for your sign-off.
  2. Approve or reject each one on its own screen, with step-up where required.

Risk manager

  1. Open Customer risk (/risk). Review the band mix and the customers whose band changed recently.
  2. Open a customer's risk tab to read the explainable score, and propose an override where the model misses something.
  3. On Risk models (/risk/models), try the What-if simulator before drafting a new model version.

Read next: Run a customer risk review.

Administrator

  1. Open Administration (/admin) and Platform health (/ops/health) to check that sources, jobs and lists are healthy.
  2. Review Tenant settings (/admin/settings): base currency, time zone, calendar, suspicion clock, required KYC, reason codes, webhooks and kill switches.
  3. Approve rules, data sources and mappings waiting in My approvals.

Read next: Administrator guide.

Integration engineer

  1. Open Data sources (/integration/sources) and connect your first source. Store the signing secret safely — it is shown only once.
  2. Build a mapping template in Mapping studio, run a dry run, then Request go-live.
  3. Once live, load files on Load data and check every run on Ingestion runs.

Read next: Integration guide.

Auditor, QA reviewer or executive

  • Auditor: open Audit trail (/audit) to see who did what and to confirm the chain is intact; Regulator reviews for sample testing; read alerts, cases and rules without being able to change them.
  • QA reviewer: work QA review (/qa).
  • Executive: open Dashboards (/dashboards) and start with the Executive overview.

Read next: Auditor, QA reviewer and executive.

Tip: Whatever your role, learn Ctrl+K (or ⌘K). Typing a name, a case number or a page name is usually faster than clicking through menus.

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.