DEV Community

Cover image for Laravel authorization and roles permission management
Amir Yousefi
Amir Yousefi

Posted on

Laravel authorization and roles permission management

You can read this post on Medium,

In many web projects, we have different user roles interacting with the system. Each role has its own permission. Every feature of the system can be enabled or disabled for these roles. We can define users permissions in our codes and check if they are authorized to do the requested action or not. A better way, mostly in more flexible systems, is to create a role and authorization management system. I’ll explain how to implement a Laravel authorization system and define users permission based on their roles.

In this post, firstly we manage users in groups we called roles. Every role has different permissions. In order to avoid permissions conflict, we assume each user has only one role. Secondly, Laravel authorization implemented by a middleware. This middleware checks for the user’s role permission and authorizes user requests.


In order to implement Laravel authorization, we will create roles and permissions table. To assign a role for users, we create a roles table. The migration for roles table is as simple as this:

Schema::create(‘roles’, function (Blueprint $table) {

We have an ID and name for roles. All users will be managed in these roles. There is also a description field, because you may need a short note on roles to describe each role for yourself.
After that, we add a foreign key, role_id, in the user table. Adding this field to the default user model helps us for Laravel authorization.


Now let’s talk about the permissions table. Every request leads to a method of a controller. So we store a list of all methods and their controller’s name in the permissions table. Later, we explain how we gather this list and how we check users authorization in Laravel by this permissions table.
Schema::create(‘permissions’, function (Blueprint $table) {

Finally, a relationship created between roles and permission.

Schema::create(‘permission_role’, function (Blueprint $table) {
$table->primary([‘permission_id’, ‘role_id’]);

We created a complete users->roles->permissions architecture. After that, an access list will be stored in these tables. So, we can easily implement Laravel authorization by checking requests against this list.

Read Laravel migration documentation for further information about creating tables.


The whole purpose of this post is about being dynamic. Especially, in systems with a different type of roles. We need to create a list of permissions in the system. Also, this list must be updated as the system developed. List of controllers and methods is a good representation of all permissions in the system. Every route is leading to a method of a controller. So, it’s a good idea to make a list of permissions using the routes list.
In order to do that, I used a Laravel database seeder. Firstly, let’s write a role seeder. It creates basic roles we need and stores them in the roles table. Running this artisan command will create RolesSeeder for you:

php artisan make:seeder RolesTableSeeder

Inside this RolesTableSeeder, we create our basic roles:

 [‘name’ => ‘admin’],
 [‘name’ => ‘operator’],
 [‘name’ => ‘customer’],

You can add as many roles as you need. Also, you can create new roles from your website whenever you need a new one.

The second step is to create an authorization list for each role. we create another Laravel seeder in which populate permissions table:

php artisan make:seeder PermissionTableSeeder

Firstly, we get all routes list. Then, We check up with the database if the permission already stored. After that, if this permission is not in the table already, we insert new permissions in the permissions table. After all, we attach all permissions to the admin role.

$permission_ids = []; // an empty array of stored permission IDs
// iterate though all routes
foreach (Route::getRoutes()->getRoutes() as $key => $route)
 // get route action
 $action = $route->getActionname();
// separating controller and method
 $_action = explode(‘@’,$action);
 $controller = $_action[0];
 $method = end($_action);
 // check if this permission is already exists
 $permission_check = Permission::where(
   $permission = new Permission;
   $permission->controller = $controller;
   $permission->method = $method;
   // add stored permission id in array
   $permission_ids[] = $permission->id;
// find admin role.
$admin_role = Role::where(‘name’,’admin’)->first();
// atache all permissions to admin role


Every request in Laravel goes through middleware. Knowing that creating RolesAuth middleware will do Laravel authorization. You can create the middleware manually or by an artisan command:

php artisan make:middleware RolesAuth

Inside this middleware, we get all permissions for logged in user. Then, we check if the requested action is in the permissions list. If requested action can’t be found in permissions list, a 403 error response returns.

// get user role permissions
$role = Role::findOrFail(auth()->user()->role_id);
$permissions = $role->permissions;
// get requested action
$actionName = class_basename($request->route()->getActionname());
// check if requested action is in permissions list
foreach ($permissions as $permission)
 $_namespaces_chunks = explode(‘\\’, $permission->controller);
 $controller = end($_namespaces_chunks);
 if ($actionName == $controller . ‘@’ . $permission->method)
   // authorized request
   return $next($request);
// none authorized request
return response(‘Unauthorized Action’, 403);

Finally, you can register this middleware in Laravel and use it according to your requirements.

Top comments (1)

bluewater0506 profile image

good post!

I have one problem. I created permission using spaite and composer require command. In migrations directory there is create_permission file exist. So, i migrated but table not created. i discovered this error when i rollback migration using php artisan migrate:rollback or php artisan migrate:reset. what is the problem? i used laravel 8 And other laravel 8 project create table but now current project is same laravel 8 but not create table and has error when rollback. also, i can see to be created personal_access_token table in current project. what is reason? Please help me.