No comments yet.
The first step to working on authorization and permissions is laying out who should be allowed to do what, and figuring out how to structure that. We’ve taken tens of thousands of hours working with engineering teams to model their authorization, pages and pages of documentation, and bottled it up into an interface that outputs a structured authorization model for developers. This helps our users implement authorization policies, but also gives them a mental model for their authorization patterns – a step that’s nearly impossible to skip, but currently time-consuming and manual.
Right now we support exports into Polar, Oso's policy language, and we're eager for feedback on what other features can be helpful for you!
We're here to listen to your feedback. We're hoping this makes writing permissions much faster and makes the learning curve a little easier.
