How Sensat Built Fine-Grained Access Control with Oso – No API Code Required!

Discover why top engineering teams trust Oso for their authorization needs!

In this video series, customers like Sensat share their experiences migrating to Oso, the challenges they solved, and how Oso improved their workflows. Whether you're exploring Role-Based Access Control (RBAC), Relationship-Based Access Control (ReBAC), or fine-grained permissions, hear firsthand how Oso helps teams manage authorization effectively.

For this video, we connected with Vlad Ursan, Engineering Manager at Sensat, to discuss how Oso transformed their authorization system. Previously, Sensat relied on a custom-built system that lacked granularity, requiring cumbersome scripts for every new project.

"Every time we onboarded a new project, we had to run a script to create policies, which was just quite a faff."

One of Vlad’s favorite things about Oso is how easy it made implementing Notion-like access control for their collaborative application.

"With Oso, we enabled permission inheritance without writing any API or database code—just by adding rules to the policy."

With Oso, Sensat built a centralized authorization model that supports fine-grained data access controls, resource inheritance, and collaborative permissions—all without modifying application code.

"It literally reads like a manifest of access in your application."

Vlad also shared how Oso made it easy to write, extend, and collaborate on policies, accelerating development.

"If I put it all together, it probably didn’t take more than a few days to write the policy—with upwards of 10 resource types and plenty of relationships."



Continue following the playlist to hear real-world insights from developers who’ve streamlined authorization with Oso!

Additional Resources
For a deeper dive into authorization, explore the following resources: 

Have questions or want to share your authorization experience? Join us on Slack, we'd love to hear from you! 

Want us to remind you?
We'll email you before the event with a friendly reminder.

Write your first policy