Security and audit

Access is defined by roles built from 73 permissions: permissions are checked both on the server and on every interface button. Data visibility can be limited to a department, and every action goes into a log whose events are signed and cannot be rewritten after the fact.

Plan All plans.

What is inside

  • Roles built from 73 permissions with “approved” and “executed” kept separate
  • Data visibility by department
  • Two-factor sign-in with a one-time code from an app
  • Sign-in through the corporate directory over OIDC and LDAP
  • Activity log with signed events and the history of each record
  • Personal data encryption and masking in the interface
  • Log export for the regulator and the auditor

Conditions

The insurer’s administrator sets up sign-in through the corporate directory.

In development

These parts of the module are on the product roadmap. We confirm timing and scope during implementation.

  • IP address restrictions and session control

Frequently asked questions

Can users sign in with a corporate account?

Yes. Sign-in through OIDC and LDAP is supported, including Active Directory.

How is the activity log protected?

Log events are signed, so any change to a record after the fact is detected by an integrity check.

Can access be limited to a department?

Yes. An employee sees contracts and claims only of their own departments if their role is set up that way.

Other features

Shall we show the system on your products?

We will build your product in the builder, take a policy from quote to claim and estimate the implementation cost for your lines of business and countries.