OneClickComply

    Role-Based Access Control

    Compliance software roles and permissions that limit who can change what

    OneClickComply includes role-based access control for IT, security and compliance leads who need to decide who can view and who can change compliance data. Five system roles cover owners, admins, editors, viewers and auditors, and custom roles let you set permissions resource by resource where your plan includes them.

    5 system roles
    owner, admin, editor, viewer, auditor
    Per resource
    permission checklist for custom roles
    Read access
    auditor role with report export
    THE PROBLEM

    Why everyone having the same access becomes an audit problem

    A compliance platform holds policies, evidence, risks and personnel records, so not everyone should be able to edit all of it. When everyone shares one level of access, a stray edit can change a control and an outside auditor sees more than they need. ISO 27001 and SOC 2 auditors expect access to be limited by role and given on the basis of need, so you need to be able to show how that works.

    FEATURES

    How roles and permissions work

    Five system roles

    Every organisation has owner, admin, editor, viewer and auditor roles. They are fixed and shown read-only in the Roles & permissions tab, so you can see what each one allows before you assign it.

    An auditor role for outside reviewers

    The auditor role gives read access plus report export, without the edit rights an editor has. It suits an external auditor or consultant who needs to look at your records rather than manage them.

    Custom roles with a permission checklist

    Where your plan includes custom RBAC roles, you can create a role and tick the permissions it needs, grouped by resource. Availability depends on plan, and the system roles stay as they are.

    Invite people into a role

    Invite team members by email and give them a role. Invitations stay pending until the person accepts.

    Two-factor authentication

    Each user can turn on two-factor authentication with an authenticator app in Settings under Security. Enforcing it across a whole organisation depends on plan and is set up with the OneClickComply team.

    Changes you can trace

    Activity in the platform is recorded in the Activity Log, so you can see who changed what and when. This gives you a record to pair with your role setup.

    See Role-Based Access Control working on your own setup.

    Book a demo
    BENEFITS

    What clear role-based access gives you

    Limit edit access to the people who own the work, and give everyone else read access

    Give an external auditor read access and report export without sharing a login

    Show an auditor how access is assigned by role, not by habit

    Build a role with only the permissions a job needs where custom roles are on your plan

    Unsaved permission changes are flagged before you leave the page, so a half-finished edit is not lost

    FAQ

    Role-Based Access Control: common questions

    Role-based access control (RBAC) means people get permissions through a role, such as viewer or editor, rather than one by one. In OneClickComply you assign a role when you invite someone, and the role decides what they can see and change.

    Every organisation has five system roles: owner, admin, editor, viewer and auditor. You can see them in Settings under the Roles & permissions tab, where they are shown read-only.

    Yes, where your plan includes custom RBAC roles. You name the role and tick the permissions it needs from a checklist grouped by resource, so availability depends on plan.

    Invite them by email with the auditor role. It gives read access plus report export, without the edit rights an editor has, so they can review your records.

    Roles and permissions help you show that access is limited by role and given on the basis of need, which auditors look for under ISO 27001 and SOC 2. They are one part of the picture, alongside your access control policy and how you review who has access.

    Yes. The Activity Log records who did what and when, with a before and after view of changes. See the audit log page for how it works.

    See Role-Based Access Control on your own stack

    Book a 30-minute demo and see how Role-Based Access Control works with the tools and frameworks you already have.