Every action, one place
Back Office and customer actions land in a single, searchable Logs center, no separate systems to reconcile.
Compliance & Security
Full Audit Trail & Activity Logs
Every action on your platform, by your team or your customers, recorded automatically in the Logs center. Tamper-evident, exportable, and ready the moment you need to prove what happened.
Logs center
Back Office
| Actor | Action type | Location | Source | Result |
|---|---|---|---|---|
| John Smithjohn.smith@company.com | Login | London, UK | Back office | Success |
| Sarah Wilsonsarah.wilson@company.com | Email Change | Lisbon, Portugal | Mob app | Success |
| John Smithjohn.smith@company.com | Suspend User | London, UK | Back office | Success |
Change details
(603) 555-0123→+44 7700 900456
Result
Success
Append-onlyEntries can’t be edited or deleted after the fact.
Export CSVAny filtered view, ready for an auditor.
Logs center
One record of everything that happened, on either side of your platform
FinHost captures Back Office actions and customer actions in the same tamper-evident system: structured, filterable, and exportable, not a raw technical log.
Actor and Target, always separated
See who performed an action and whose account it affected: captured as distinct, structured fields, never conflated.
Tamper-evident by design
Append-only, non-editable records that hold up under audit, dispute, or investigation.
Before-and-after on every change
Phone numbers, emails, MFA settings, see exactly what changed, not just that it did.
Filter down to one event
By actor, target, action type, source, date range, or account/transaction ID.
Export when you need it
Pull any filtered view to CSV for auditors, regulators, or your own records.
From action to evidence
Every entry follows the same five steps
No opt-in, no manual logging the record builds itself as your platform is used.
Something happens
A teammate or a customer performs an action, anywhere on the platform.
It’s recorded automatically
Every relevant action lands in the Logs center by default, nothing to switch on.
Actor and Target are captured
Who did it, and whose account it affected, saved as separate, structured fields.
Details are preserved
Before-and-after values, IP/location, source, and exact timestamp (UTC) are saved with the entry.
It’s there when you need it
Filter, open the detail view, or export to CSV the record doesn’t change after the fact.
LOGS CENTER↑ EXPORT CSV
| Actor | Action type | Location | Source | Result | |
|---|---|---|---|---|---|
| John Smith | Logout | London, UK | Back office | Success | VIEW → |
| Sarah Wilson | Email Change | Lisbon, Portugal | Mob app | Success | VIEW → |
| John Smith | User Invited | London, UK | WEB client | Success | VIEW → |
Filter your way
See every action, filtered the way you actually need it
Start from the actor or the target account, then narrow from there.
- Filter by Actor (ID, email) or by Target, never mixed together
- Source narrows to Back office, Web client, or Mobile application
- Date presets (last 7/30 days) or a custom range, down to the day
Detail view
Every change, before and after
Open any entry and see exactly what happened, not just that something did.
- Actor’s name, role, email, IP address, and ID, always attached
- Change details show the “from” and “to” value, side by side
- Related Activity shows other recent actions by the same person or account
LOGS CENTER · DETAILSAdmin Action
Full name
John Smith
Role
Admin
Action type
Phone change
Location
London, UK
Change details
(603) 555-0123→+44 7700 900456
Why FinHost
Built to be handed to an auditor, not just read by engineers
Built for proof, not just debugging
Structured for auditors and investigators: Actor, Target, Result, and before/after values, not raw technical output.
Two audiences, one record
Staff actions and customer actions land in the same tamper-evident system, not separate tools you have to reconcile.
Works with your access controls
Who can view the Logs center is already governed by Role-Based Access Control: Admin, Compliance, and Support roles included by default.
Coverage
What gets logged
Back Office actions
Admin changes, account edits, manual transaction reviews, provider configuration.
Customer actions
Logins, transfers, profile changes, MFA and security settings.
Financial activity
Transaction approvals, card operations, exchange orders, transfer orders.
Security & access
MFA method changes, biometric enrollment, password resets, administrator changes.
Exports & requests
Every data export and manual account request is itself a logged, auditable action.
Related FinHost modules
Works alongside the modules that create the activity it records
See your platform’s activity, end to end
Every action, tamper-evident and exportable, ready the moment you need to prove what happened.
LoginLondon, UKBack office · Success
Phone changeLondon, UKBack office · Success
Suspend CardLisbon, PortugalBack office · Success
LogoutLondon, UKBack office · Success
Frequently Asked Questions
What’s the difference between this and Role-Based Access Control?
Role-Based Access Control decides who is allowed to do what. The Logs center records what actually happened, including who viewed or changed anything. They’re complementary: viewing the Logs center itself requires the right RBAC permission.
Can a log entry be edited or deleted after the fact?
No. Entries are append-only and non-editable by design, so the record stays reliable for audits and disputes.
How long are logs retained?
Retention is typically tiered by action type, financial activity is kept longer than routine login activity. Confirm exact periods with your account team before relying on a specific figure for your compliance program.
Can I export logs?
Yes. Any filtered view in the Logs center can be exported to CSV directly, ready to hand to an auditor or regulator.
Does this log actions from customers too, or just Back Office staff?
Both. Actions taken by your own team and by your end customers are captured in the same system, with the same Actor/Target structure.