Hear from our customers
“Arc is a banking platform, so getting authorization right is critical. We knew our requirements could get complex – we’ve already got 40 permissions across 9 roles – and we wanted to lean on the experts.”
“Oso is excellent and well worth taking a look at. The rollout at Intercom has been very slick."
Common Use Cases
Take the first step – separate users by organization to keep their data separate from each other. Get the multi-tenancy policy.
Group permissions by feature, project, or whatever criteria make sense for your app. Read the RBAC guide.
Files & folders
Ownership & sharing
Let your users create their own roles based on their requirements. Get the custom roles policy.
Show or hide elements in your UI based on your users’ permissions. Learn about authorization in the UI.
Beyond just, "Can this user access this resource, yes or no?" ask, "What are all the things resources this user can access.” Read the data filtering guide.
Control who can create, update, and delete resources. See an example.
Ask arbitrary questions
Sometimes you need ask arbitrary questions like, “Who are all the users that can write to this repo?” Read the Query guide.
When you get an unexpected result, inspect the specific logic and data used to generate an authorization decision. Learn about debugging with Explain.
See logs of authorization decisions to confirm that your system is working as you expect it to. Try it in the sandbox.