Skip to content

Solution

System Governance & Security Architecture

Named logins, role permissions, full audit trail, isolated data

A permission matrix per role, audit and reversal logs, password policy, instant revocation of app access, one database per institution and encrypted provider keys.

Each institution runs on its own database; staff of one bank cannot reach another's data, and the database can be exported or restored independently. Inside the institution, a permission matrix defines what each role can view, create, edit, delete and approve, managed on screen by your administrator without any code change.

Every login and posting is recorded against the named staff member. Backdated postings are logged as a distinct event. Passwords must be changed within seven days of issue and rotated every ninety, and deactivating a staff member revokes their web and mobile access instantly.

What it does

  • Role permission matrix managed on screen
  • Audit log of every login and posting, with backdate events flagged
  • Reversal history: nothing deleted, everything traceable
  • Password expiry and forced change of initial passwords
  • Instant revocation of mobile tokens on deactivation
  • One isolated database per institution
  • Encrypted storage of SMS, payment and identity provider keys
  • HTTPS everywhere with daily off-site backups

How it works

  1. 1

    Define roles and tick the permissions each one gets.

  2. 2

    Assign staff to roles and branches.

  3. 3

    Review the audit log and reversal history at any time.

  4. 4

    Deactivate a leaver and their access ends immediately.

Related

Works together with

See System Governance & Security Architecture on a live demo

A live demonstration on a sandbox with sample data, then a free two-day data assessment for a fixed go-live date.

Prefer WhatsApp? Chat with us