Gates are simple closures defining whether a user can perform an action (Gate::define('edit-post', ...)), useful for actions not tied to a specific model. Policies are classes organizing authorization logic per model, with methods like view, update, and delete, and are checked via $this->authorize() or @can in Blade. Policies are auto-discovered or registered in a service provider.
← Laravel theorytheory 0/50 · 0%
level 1
Curious · 0 XP
streak
0d
perfect
0
badges
0
100 XP to Apprentice
Auth · medium
28. Authorization: Gates & Policies
Controlling access to actions.
1 min read2 questionsup to 50 XPtopic 28/50
Read in another language
AI translates the explanation and quiz text while preserving code and answer scoring.
How to study this topic
- 1. Read the explanation once end to end, skipping the code.
- 2. Re-read the code snippets and say out loud what each line does.
- 3. Answer the quiz without scrolling back — that is the real check.
- 4. Read every explanation, even for the answers you got right.
Scoring
- · Up to 30 XP from quiz accuracy.
- · +15 XP for a perfect first attempt.
- · +5 XP while a 3-day streak is running.
- · 75% or higher marks the topic complete.
Check your understanding
1. When should you prefer a Policy over a Gate?
2. Which Blade directive checks authorization?
Badges
First light
Pass your first topic
Sharp shooter
3 perfect first-try quizzes
On a roll
Study 3 days in a row
Week warrior
Study 7 days in a row
Grinder
Earn 500 XP
Deep diver
Earn 1500 XP