Model Common Use Cases

Model Common Use Cases

The first step in using Oso to power your app's authorization is laying out who is allowed to do what. We call this your authorization model, which you express as rules.

Some example models are:

  • Multitenancy: what the user can do is based on their role in the organization they belong to.
  • Resource-specific roles: users and resources are grouped into core business concepts like teams and projects. Users can create resources and share these with other people. Your access is dictated by what role you've been granted on any/all of these teams, projects, resources, etc.
  • Custom roles: using a predetermined set of permissions, admins can create their own custom roles to match the nuance of their business.

Here are 3 resources that would be useful to have open when running through these guides:

If you're getting started with authorization, the most common starting place is the Roles (RBAC) use case.