Pick a language:

Enforce an Oso Policy

To use an Oso policy in your app, you’ll need to “enforce” it. A policy is useless without an app that consults the policy on user actions. For most apps, policies can be enforced on multiple “levels”:

Resource-level: is the user allowed to perform this action on a particular resource?
Field-level: which fields on this object can the user read? Which ones can they update?
Request-level: should this user even be able to hit this endpoint, regardless of the resources it involves?

Oso provides an API to enforce authorization at all levels, each of which are described in this guide.

We recommend starting out by reading about resource-level enforcement.

Resource-level Enforcement

Learn about enforcing request-level authorization, controlling who can perform which actions on which resources.

Field-level Enforcement

Learn about enforcing field-level authorization, controlling who can access which fields of your resources.

Request-level Enforcement

Learn about enforcing request-level authorization, controlling who can access which routes or endpoints in your app.

Connect with us on Slack

If you have any questions, or just want to talk something through, jump into Slack. An Oso engineer or one of the thousands of developers in the growing community will be happy to help.