Setup & Clients

Clients & Tenants

Every organisation is a dooit client: MLTFPD as supervisor and each bank, MFS provider and NBFI as a reporting organisation · data is isolated per tenant

How tenants are kept apart

Data

Separate database schema per client, row-level security on shared services

Keys

Each client has its own key-encryption keys in its own HSM partition

Network

Per-tenant namespaces with default-deny network policies

Identity

Separate realm per client; supervisor access is read-only and logged

Models never train on one client’s data for another without consent

Logs

Per-tenant hash chains; the supervisor can verify but not edit

Tenant access rule

allow(request) if
  request.tenant = resource.tenant
  or (request.role = supervisor and resource.shared_with_supervisor
      and request.legal_basis != null)          # logged, read-only
key = HSM.partition(resource.tenant).kek       # no cross-tenant keys