Security
How Monival separates your organisation's data from every other organisation's, and who can access it. We'd rather you read this once than find out by asking.
Tenant isolation
Monival is multi-tenant: every organisation’s forms, submissions, indicators, and reports share the same application and database, separated by an organisation identifier attached to every record. Every query the platform runs is scoped to the requesting user’s organisation — there is no view, report, or API endpoint that returns another organisation’s data by default.
This is row-level isolation, not physically separate databases per customer. If your organisation’s data must be physically isolated from every other tenant — a common requirement for government and large institutional donors — a dedicated instance is available on our Premium plan. Talk to us about what that involves.
Who can access what
Access inside an organisation is controlled by role: Monival enforces role-based permissions on the server, not just in what the interface shows you. Roles determine who can design forms, who can review and approve submissions, who can see financial data, and who administers the organisation’s account. You assign roles to your own team members; we don’t have a back door around them.
Programmatic access — for a BI tool pulling the OData feed, or a script hitting the REST API — uses scoped API keys that you generate and can revoke at any time, with an optional expiry.
Signing in
Monival supports email/password sign-in and “Sign in with Microsoft” for organisations already on Microsoft 365. If your organisation needs SAML-based single sign-on, talk to us — this is evaluated case by case, not shipped as a self-serve toggle today.
Data in transit and at rest
All traffic to Monival — the web app, the mobile app’s sync, the API — is encrypted in transit over HTTPS. Media you collect (photos, signatures, audio) is stored on our servers, not distributed to third-party object storage.
What we haven’t published yet
We don’t currently publish a list of compliance certifications, a data-residency statement, or a formal audit log for every account action — we’d rather say nothing than overstate what exists. If any of these are a requirement for your procurement process, get in touch and we’ll tell you exactly where things stand.