Skip to content
Go to homepageDrova logo
This is a Drova Labs prototype. Still taking shape, but ready to try today. Explore Labs for free

Role-based access controlfor risk and compliance

Open Drova to the whole business, without opening everything to everyone.

Inviting someone into most platforms means making them an admin. So you over-share, or you keep people out and do their work yourself. This prototype gives each person exactly the access their job requires, keeps it right as people change, and makes it easy to show an auditor.

The role-based access control prototype: positions, a team's security settings, and inviting a person, in one window

The problem

Everyone's an admin, or nobody gets in

Risk and compliance teams of one to three, answerable to a board, auditors and a regulator, want the whole business working in one place: first line included, auditors included, with sensitive records seen only by the people entitled to them. The tools on offer trade control for effort. Deep control takes a specialist and a course. Easy tools over-share. So the register stays in a spreadsheet with one owner, or everyone gets admin and hopes for the best.

Two things we hold the design to: protecting a record in Drova should be no harder than keeping a private spreadsheet, and nobody should need a course to use it.

Positions, not people

Access follows the position, not the person

A position is a job someone holds, not the person holding it. Its teams decide what it can reach. When the Compliance manager changes, the new person steps into the same access on day one, and nothing has to be rebuilt or remembered. In the prototype, positions sync from the HR system, so the org chart is the starting point.

Five values, one sentence

Exactly what the role needs, and nothing more

Every team gets one level per record type: View, Create, Update, Delete or Set security. Each box includes the ones before it, so there is one sentence to read and one to set. Give the compliance team Update on controls and they can do their job without a single risk or event opening up alongside it.

Prepared, checked, switched on

Nothing goes live until you switch it on

Add a person and they start as Not yet invited. Check what they will reach, record type by record type, before any invite goes out. Then switch them on. An external auditor can be prepared with the access they need, checked, and invited only when you're sure. Nobody has to create a test account to find out what a new starter will see.

Three steps to try it

A few minutes gets you inside the prototype, and a say in it.

Create a free account

The same account you'd use for the platform. Sign up, verify your email and you land in Drova Labs.

Open Role based security and permissions

Take the short tour, then set up a team, a position and a person on the sample tenant.

Tell us what would make it work for you

Share feedback from inside the prototype. It goes straight to the people building it, and we report back what changed.

Role based security and permissions is open in Drova Labs now, and your view can still change it.

Try it before it ships

Role based security and permissions

Questions and answers

Is this in the product today?

Not yet. It's a working prototype in Drova Labs, built on a sample tenant, so you can try the model while it's still taking shape. We say so in Labs and in New Frontier when it ships.

What can I try right now?

Positions that hold access, teams with one level per record type, and the prepare, check, invite flow for a new person. The items under "Where this prototype is heading" come after that.

What comes after this?

The next steps on the roadmap, in order: explaining any access in plain words, permissions that follow your org structure, changing many things at once, answering the auditor from the system, governed AI, and sealed types with field-level security. Express interest in any of them from inside Labs.

What happens to my feedback?

It goes straight to the person building the prototype. We report back what changed, in Labs and by email.

Does it use my data?

No. The prototype runs on a sample tenant, and you're never asked to upload anything to try it.