Rather than spending hours reading documentation, build your permissions with the Modeler. Just answer a few prompts about your application and you'll get a structured authorization model in return.
When we talk to developers about authorization, their number one challenge is getting their heads around how to model their permissions. We're so excited to launch this tool for the community to get a better grasp of authorization permissions.
This along with our resources like Authorization Academy (osohq.com/academy) are a great way to get started with writing authorization. Thanks @cuffejamie for the launch support today! I've learned so much from the team at @retoolapp and I am excited to continue to learn from y'all!
@cuffejamie@retoolapp@francium@perte Great question. Working with our target users to get the language right in the use case sentences we canned took a lot of time. What made sense to us initially was pretty far away from what made sense to users, and therefore what we landed on in the end.
We have to be precise with our words because we offer the ability to convert the personalized version of those sentences (using your nouns and verbs) into logic expressed in our authorization-as-code policy language called Polar.
Oso Modeler let's you model your authorization in minutes. Skip the docs and get an authorization model you can use out of the box. Check it out and congrats to the Oso team on a great launch!
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 interactive interface that gives developers a structured authorization model. This helps developers not just implement, but importantly it gives them a mental model – a step that’s nearly impossible to skip, but currently time-consuming and manual.
We’re eager to get this in your hands and hear your feedback!
Modeling is one of the hardest pieces of the authorization puzzle. Especially when you've already defined your system using different nonstandard terms, it's difficult to have the right language for what your system even needs to support. This is a neat product to help standardize the way we talk about these concepts!
WebRemarks
Retool
Oso Cloud