Security & Access

Permissions

Layer organization, group, program, functional, and object-level access without making everyone an administrator. Roles and inheritance let you set a grant once and keep it correct as the work changes.

Base roles for the common cases

Most people are covered on day one, without a policy workshop to decide who can do what. Assign a base role at the organization level and someone has a sensible default for everything they touch.

Owner, Admin, and Member roles for the common cases
Read-only access for the auditors and executives who only need to look

ORGANIZATION ROLESSENSIBLE DEFAULTSOwnerFULLSuper adminADMINISTERAdminMANAGEMemberCONTRIBUTEAuditorEVIDENCELayer on roles for more access without full permissions

Additional roles for the exceptions

Programs have exceptions: a contractor who should see one framework, a vendor manager who edits vendors and nothing else, an auditor who reads evidence for a single period. Layer additional roles on top of the base role, scoped to the objects that matter.

Layered on top of a base role, never replacing it
Grant to one person or to a whole group

Alina FerreiraCONTRACTOR · VENDOR REVIEWMEMBERADDITIONAL ROLE, SCOPEDRisk managerSCOPED TO · VENDOR RISKEVERYTHING ELSEBASE ROLE APPLIESGRANT TOUSER OR GROUPLayered on the base role, not a replacement for it

Grant access once, not everywhere

Grant access once and let it reach everything it should, instead of re-granting it object by object. Permissions flow down from a group to its members and from a parent object to what's attached to it, so a single change lands everywhere it belongs. API tokens follow the same model.

Add someone to a group and their access follows automatically
API tokens scoped by object and action, revocable one at a time

PERMISSIONS FLOW DOWNPlatform groupGRANTEDEvery member of itINHERITEDObjects attached to itINHERITEDAPI TOKENS FOLLOW THE SAME MODELAn integration tokenORG SCOPEDSCOPED TOA SPECIFIC OBJECT TYPEOPERATIONSREAD / WRITE / DELETE

Least Privilege by Default

Access at the level of the work

Openlane governs access in real time, at the level of the work — from the whole organization down to a single object. Roles and inheritance give you a grant that fits the task, so access stays correct as work changes instead of being reconstructed in a periodic review.

Least privilege, made easy

Narrow access is the path of least resistance. Nobody grants admin because scoping the permission properly would have taken longer.

Tokens with a bounded blast radius

Every API token is scoped and revocable, so an automation that reads evidence can't quietly rewrite your control set.

Answers for access reviews

Who can see this, how did they get access, and through which group — each question has a lookup instead of a reconstruction.

Trusted By