Why it exists
Why Warrant — the problem with the usual policy-and-query approach, and what Warrant does instead.
Laravel Warrant
A small DSL language that converts portable conditional permission rules to sql to make row level access control centralized and flexible.
Warrant lets you write your access rules once — as small, portable strings — and compiles them straight to SQL. One rule set answers “can they?”, filters a list, and tells you what a user can do to each row, with no permission tables to migrate and no policy logic duplicated across your app.
if is_my_own_document or manages_team they can view, updateif is_document_locked and not is_admin they cannot view, updateif is_admin they can *New here? Why Warrant walks through the problem it solves and how it works.
Start here
Section titled “Start here”Install & first check
Installation then the Quick start — a schema, a rule, a resolver, and the checks that use them, end to end.
The mental model
Core concepts — how schemas, rules, and the resolver divide the work.
Build for real
The Guides go deep on schemas, conditions, the rule language, resolvers, context, middleware, and testing.
Look something up
The API Reference has the cheat sheet, full signatures, and the complete error catalogue.