Two-factor for password sign-in
Every member of staff signing in with a password proves a second factor with an authenticator app, and gets recovery codes that each work once.
Who can sign in, what they can do, how long data is kept, and where it’s held are all set in Casebridge, where your admins can check them.
Every member of staff signing in with a password proves a second factor with an authenticator app, and gets recovery codes that each work once.
Staff can sign in with their Microsoft account, and you can make it the only way in for your organisation.
Common passwords, ones about the account, and ones found in known breaches are refused.
A session ends after an hour without use, and after twelve hours at most.
Each member of staff is an owner, admin, or officer. Only owners and admins can change forms, Case types, integrations, and settings.
Every query is scoped to one organisation, and the database’s row-level security enforces it as well.
Each Case type says which roles can view its Cases, move them between stages, assign them, and edit their data. Change it there, and it applies to every Case of that type.
Each kind of data has a retention period, adjustable within set limits. When it ends, the data is deleted or anonymised, depending on what it is.
Export everything held about a person as one download, or erase it once nothing still needs it.
Forms, Cases, people, records, and account security each keep a history of who changed what and when.
Casebridge’s own logs hold identifiers and codes, never what a resident told you.
Your data, and the servers that read and write it, are in Microsoft Azure’s UK South region, with the database backed up automatically.
Integration keys and two-factor secrets are stored encrypted, and the keys that protect integration keys are held in Azure Key Vault.
In Microsoft Azure’s UK South region: the database, uploaded files, and the servers that read and write them.
Yes. Staff can sign in with their Microsoft account, and an owner can make it the only way in. Microsoft’s own sign-in rules, including its multi-factor authentication, then apply.
Admins edit a draft and submit it for review. It goes live only once it’s approved, and approval is refused if it changed after it was submitted. Every version stays on record.
Each kind of data has a retention period you can see and adjust within limits. When it ends, the data is deleted or anonymised, depending on what it is.
Tell us which service you have in mind, and we’ll show you how it would work in Casebridge.
Contact us