Administrator and integration engineer
Administrators run the institution's settings, data and governance; integration engineers connect the systems that feed FlowSentry.
tocOn this page
Administrators look after your institution's FlowSentry workspace: its settings, its data connections and its governance views. Integration engineers are usually from your IT team and connect the core banking, mobile-money or brokerage systems that send data in. The two roles work together: the engineer builds and requests, the administrator approves.
Important: Multi-factor authentication is mandatory for administrators. On first sign-in you are sent to Security & MFA (
/account/mfa) to enrol before you can continue.
Administrator
What you can do
- Propose and approve changes to Tenant settings: base currency, time zone, business calendar, the suspicion clock and required KYC fields.
- Turn Kill switches on or off (client onboarding, identity verification, AI features), each with a reason and a fresh second factor.
- Register outbound webhooks and maintain the disposition reason codes analysts use.
- Connect data sources, approve go-live, and approve mapping templates.
- Upload files and correct quarantined rows in ingestion runs.
- Maintain FX rates used to normalise amounts.
- Approve or reject monitoring rule versions.
- Propose list changes and good-guy exclusions.
- Read the Audit trail, including the chain integrity check, and run Regulator reviews.
- Watch Platform health: scheduled jobs, source freshness, webhooks, platform lists and AI usage.
- Set up client onboarding journeys in Onboarding setup, when onboarding is switched on.
- Use the dashboards, including AI usage.
What needs a second person
You need a second administrator. Tenant settings change under maker-checker: one administrator proposes, a different administrator approves with a fresh second factor. Plan for at least two administrators at your institution.
| You make | Who checks | Step-up |
|---|---|---|
| A tenant settings change | Another Administrator | Yes |
| A list change or exclusion | MLRO, Deputy MLRO or Screening checker | Yes |
You are also the checker for others:
| They make | You check | Step-up |
|---|---|---|
| A data source go-live request | Administrator, not the requester | Yes |
| A mapping template version | Administrator, not the author | Yes |
| A rule version | Administrator, MLRO or Deputy MLRO, not the author | Yes |
| A settings change by another administrator | You | Yes |
Kill switches, webhooks and reason codes apply at once, without a checker, and every change is audited.
What you cannot do
- See alerts, cases, customers or STR material. Administration is separate from investigation.
- Approve your own settings change, go-live request or mapping.
- Approve list changes or exclusions.
- Manage users and roles in the product. There is no self-service user-management screen yet: accounts and roles are set up for your institution during provisioning. Ask your FlowSentry contact to add a user or change a role.
- Run platform-wide jobs or provision institutions. That is the FlowSentry service team's job.
Integration engineer
What you can do
- Connect a source on Data sources: name, connector, data it sends, rate limit and silence SLA. The signing secret is shown once: copy it and store it securely.
- Test with the validate-only API while the source is in Testing, then Request go-live.
- Rotate key or Revoke now on a source's signing key, with a fresh second factor.
- Build mapping templates in the Mapping studio: infer from sample rows, map fields, preview, and send for approval.
- Upload files on Load data and work quarantined rows on Ingestion runs.
What you cannot do
- Approve a source's go-live or activate a mapping template. An administrator approves.
- See alerts, cases, customers or tenant settings.
Warning: A signing secret is shown only once and is never shown again. If it is lost or exposed, rotate the key straight away.
Where you work
| Page | Route | What for | Roles |
|---|---|---|---|
| Tenant settings | /admin/settings |
Settings, kill switches, webhooks, reason codes | Administrator |
| Administration | /admin |
Hub of administration cards | Administrator |
| FX rates | /admin/fx |
Rates used to normalise amounts | Administrator |
| Platform health | /ops/health |
Jobs, sources, webhooks, lists, AI usage | Administrator |
| Audit trail | /audit |
Audited activity and chain integrity | Administrator |
| Regulator reviews | /regulator/reviews |
Examiner-ready sample reviews | Administrator |
| Data sources | /integration/sources |
Connect sources, keys and go-live | Both |
| Mapping studio | /ingestion/mapping-studio |
Map source fields | Both |
| Load data | /integration/files |
Run a file through a source | Both |
| Ingestion runs | /integration/runs |
Results, quarantine and corrections | Both |
| My approvals | /approvals/inbox |
Go-live, mapping, rule and settings approvals | Both |
Your first steps
- Enrol your authenticator app and add a passkey from the user menu.
- Administrators: open Tenant settings and confirm base currency, time zone and business calendar.
- Check FX rates: a missing rate means rules with thresholds in that currency cannot evaluate.
- Integration engineers: open Data sources, connect your first source and run a dry run.
- Build and preview a mapping template, then request go-live.
- Administrators: approve go-live and the mapping from My approvals, then check Platform health.