Manage tenant settings and kill switches

Tenant settings hold the choices that apply to your whole institution. Core settings change only when two administrators agree. Kill switches, webhooks and reason codes apply straight away but are still recorded in the audit trail.

Before you start

• You need the Administrator role.
• Core settings need two different administrators: one proposes, the other approves with a fresh second factor (step-up).
• Turning a kill switch needs a reason and step-up.
• Open Tenant settings from the Admin module, or go to /admin/settings.

Change a core setting

The core settings are:

Setting	What it controls
Base currency	The currency amounts are normalised to
Time zone	For example East Africa Time (Nairobi)
Business calendar	Kenya public holidays or weekends only, plus gazetted holidays
Suspicion clock (business days)	How long the MLRO has to decide a recorded suspicion, from 1 to 30 days; the default is 2
Required KYC for individuals and for organisations	The KYC items a customer must have to count as complete

Until your institution approves its own values, FlowSentry uses Kenyan shilling, East Africa Time, the Kenyan calendar and a two-business-day suspicion clock.

Propose

1. Select Propose a change.
2. Edit the values.
3. Select Submit for approval.

You can Withdraw the proposal until it is decided.

Approve

1. A different administrator opens Tenant settings, or the item in My approvals at /approvals/inbox.
2. They review the proposed values against the current ones.
3. They select Approve, confirming with a fresh second factor, or Reject.

Every approved version is kept in the versions history, so you can see what changed, when and who agreed it.

Warning: Changing the base currency or business calendar affects thresholds, deadlines and figures across the product. Agree the change with your MLRO before you propose it.

Use a kill switch

Kill switches turn a whole feature off for your institution at once. The switches are:

• Client onboarding (CLM)
• Identity verification
• AI features

To turn one off or on:

1. In Kill switches, select the switch.
2. Give a reason.
3. Confirm with a fresh second factor.

The change applies immediately and is recorded with your name and reason.

Tip: Use the AI features switch if you need to pause all AI assistance quickly, for example during a data protection review. Assistants then fall back to rules-based summaries where they can, labelled "Generated without AI — rules-based summary".

Register an outbound webhook

Webhooks let FlowSentry notify your other systems when something happens.

1. In Outbound webhooks, select Register an endpoint.
2. Enter the Endpoint URL and choose the events to send.
3. Save.

Every delivery is signed with an HMAC signature header (X-FlowSentry-Signature) so the receiving system can confirm it came from FlowSentry. Failed deliveries are retried with increasing gaps. Recent deliveries shows each delivery and its attempts.

Note: Make sure the receiving system checks the signature on every delivery and rejects anything unsigned or altered.

Maintain disposition reason codes

Reason codes are "The reasons analysts pick when they close an alert".

• Select Add or reword a code to create a code or change its wording.
• Select Deactivate to stop a code being offered to analysts.

Changes apply at once and are recorded in the audit trail. Keep the catalogue short and clear; analysts and QA reviewers rely on it.

Related

• Administrator guide
• Check platform health and scheduled jobs
• Use AI assistants responsibly
• Administrator and Integration engineer