Security & compliance
Built to survive a peer review.
Access is a permission model, not a job title. Overrides are possible, and expensive: each one demands a written reason and writes a high-severity row to the tenant audit log.
Authorisation
Nobody can grant what they do not hold.
Define roles at the permission level (eighty of them) and call them whatever your firm calls its people.
Permission ceiling
Access simulator
If approved, A. Menon can open 412 client records, 9 report types and no payment screens.
A role manager proposes; an approver reviews. The proposal, the approver and the resulting permission set are all recorded: the before and the after, not merely that something changed.
Before granting anything, the access simulator answers the question a partner actually asks: what will this person be able to open? Every member can see their own effective permissions too, so there are no surprises on either side.
Controls
Nine of them, one line each.
Data handling
Our current posture, rather than badges we haven't earned.
Identity
- Authenticator MFA with backup codes
- Trusted-device list, revocable by the member or an admin
- Step-up authentication for payments and role changes
Your data
- Tenant export on request, at any point in the contract
- Anonymisation on request when a firm leaves
- Nightly tenant backups
Consent
- Transactional, billing, portal and compliance messages: opt-out
- Marketing messages: opt-in only
- Hard bounces and complaints suppress the address automatically
Request the security pack.
Controls list, data-residency options, sub-processor register, DPDP alignment statement and the DPA, sent the same day by a person.