Separation between authorities
The database separates each authority’s data on every table that carries one. An automated test checks that all these tables apply the separation. A deactivated authority no longer receives any input.
Security and hosting
Separation between authorities, permissions, log, backups and reversibility.
The database separates each authority’s data on every table that carries one. An automated test checks that all these tables apply the separation. A deactivated authority no longer receives any input.
Permissions depend on each user’s role and entity. Delegations are dated. Sensitive approvals require a person other than the author and the last participant.
The authority can require a one-time code for all its accounts. This setting is disabled by default; every change and its author are kept in the log.
The log keeps track of changes. Third-party identifiers are encrypted in the database, and reading them requires a specific permission.
Incremental file backup is encrypted, with an off-site copy. A full restore from that copy alone has been carried out as a trial. The location, frequency and destination of copies are set for each deployment.
A complete archive of the authority can be prepared on request: data, documents, configured fields, formulas, packs and settings, including deactivated modules. Downloading it is restricted to authorised administrators and recorded in the log.
The hosting location and data residency are decided with the authority, for each deployment.
When a buyer requires it, the source code is deposited with a trusted third party.
Bring your specifications or your security questions. We answer them point by point during the demonstration.