Skip to main content

Launch Week, Day 5 - Authorization Model Starter Templates

· 4 min read
Aditya Kajla
Co-Founder @ Warrant

Launch Week, Day 5

Happy Friday! It's the final day of Launch Week! In case you missed the previous days, you can catch up here: Day 1, Day 2, Day 3 and Day 4.

Throughout the week, we've talked about various nuts & bolts upgrades to the Warrant platform that bring improved performance, resiliency, and safety to the APIs and core authorization service.

Today, we're excited to introduce Warrant templates, a repository of pre-defined and purpose-built object types schemas designed to get you up and running with Warrant in minutes. Simply pick a template that matches your application use-case and deploy it into your Warrant environment using the CLI. Each template also ships with a test suite with sample tests, making it easy to iterate.

We're launching with 4 brand-new templates today, all of which represent common use-cases we've seen developers build with Warrant. Many of these templates make use of the built-in object types already present within Warrant (e.g. roles, permissions) with added object types for more bespoke scenarios.


First up, is a template to model access control within a developer tool. Modern devtools, although focused primarily on the developer experience of their APIs and tooling, are becoming increasingly collaborative. If you're building a devtool and looking to set up a multi-tenant access model that supports multiple users per tenant, custom teams (also per tenant), as well as custom applications and/or projects, this template will get you up and running in no time.

Document store

The document store template is perfect for anyone building an application with user-generated content that requires 'Google Docs' like sharing and access control. Using the document and folder object types, you can easily create document hierarchies per user and/or team.

Enterprise access control

A common use-case we often see is internal IT teams looking to build out an enterprise access control system for their organization. Typically, these systems are required to control employee access to vendor-provided software as well as custom, in-house applications. The enterprise access control template is designed for this use-case and comes with organization, team and employee object types that make it easy to set up organization hierarchies and application or environment-specific access rules.


Another common internal access control use-case we've come across is 'infrastructure access', typically required in larger companies with multiple teams that have adopted a microservices (or even just service-oriented) architecture. In such models, developers, teams, and even machines, are granted read or write access to specific services based on organization and team hierarchies. If you're looking to build out such an access model, check out this template here.

What's next

We believe that these templates represent a handful of the common use-cases and access models that developers are looking to add into their applications. But they're by no means exhaustive. We intend for this templates repository to be a living template store and will continue to update it and add new templates over time. That being said, if you have any ideas for new templates, or would like to contribute your own, join us on Slack and let us know!

With that, we're at the conclusion of our first ever Launch Week! Thanks for following along with us this week and we hope you're excited about all the new updates and features we've shared!