mabrouk/permission

a laravel package to handle dealing with permissions in custom groups

2.1.0 2025-06-17 07:08 UTC

Requires

• laravel/framework: >=9
• mabrouk/filterable: >=1
• mabrouk/translatable: >=1

Requires (Dev)

• orchestra/testbench: ^7.0@dev

MIT

• Ahmed Mabrouk

README

mabrouk/permission is a Laravel api package for dealing with project admins permissions using Database approach.

Table of Content

Important Introduction

Usage sequence

Installation

Configurations according to project needs

Using HasPermission Trait on desired models

Out of the box methods and attributes

• Methods
• Attributes

Out of the box models

Out of the box routes

What else?

Models Api Resources to expect in requests response

Any thing else?

License

Important introduction

In order to get the most benefit of this package results, try to follow the standard routes naming to have a well organized permissions names suites very well with your models naming as well.

• avoid using verbs in routes naming such as get_users and get_news, instead use the model plural name will fit very well here trust me.

Usage sequence

After installation and modifing configuration:

• add new routes -if you don't have some- which have one of the basic urls in config file
• run command php artisan permission:seed when you need to apply permissions on newly added routes.
• include predefined routes which control permission groups, Roles, and permission display names in your api documentation to make it available for implementation from frontend developer working on admin-panel or any dashboard you specified its api base url in permissions.php config file. or guide frontend developer to this documentation Models Api Resources to expect in requests response section

Installation

You can install the package using composer.

composer install mabrouk/permission

In order to get things work, add the PermissionOfficerMiddleware at the end of the $routeMiddleware property of app/Http/Kernel.php class

    protected $routeMiddleware = [
        // ...
        'permission-officer' => \Mabrouk\Permission\Http\Middleware\PermissionOfficerMiddleware::class,
    ];

After this you may accept it on any specific grouped routes like api group under $middlewareGroups property in same kernel file or use it on specific routes in your routes file as most of middlewares you used to use before.

The first option to apply it to api group for example will be more comfortable during development process as you will not have to think about it anymore after configuring package configuration with your project needs.

    protected $middlewareGroups = [
        'api' => [
            // ...
            'permission-officer',
        ],
    ];

• Now you need to run the following command in order to publish package migrations and publish permissions.php config file to config directory

php artisan permission:setup

• Then you need to run the following command in order to migrate package tables

php artisan migrate

Configurations according to project needs

Config file have several configuration options and already have enough comments to describe every key meaning and how to use.

You may access it under config/permissions.php

After modifying permissions.php config file don't forget to run below command:

php artisan config:cache

Using HasPermission Trait on desired models

Now you need to add Mabrouk\Permission\Traits\HasPermission.php trait on models which will have roles such as "User" model for example. Don't forget to add this trait to all models you specified in permission.php config file under the key roleable_models and don't forget to carefully read the instructions included in config file.

• You are all done with installation and structure. Now we need just to understand how to use it.

Out of the box methods and attributes

After using Mabrouk\Permission\Traits\HasPermission.php trait on specified models in permissions.php config file as mentioned above you will have additional methods and attributes on specified models. let's take User model as example and see methods usage such as the following:

Methods

• $user->roles() This is the relationship method and how to access roles as a laravel normal relationship method. Put in mind that it's a polymorphic relationship so to get reversed relation $role->users() the users() method here will have the same name as specified model key in permissions.php config file under roleable_models key.

• $user->permissions() This is the relationship method and how to access permissions as a laravel normal relationship method.

• $user->subPermissions() This is the relationship method and how to access sub-permissions as a laravel normal relationship method.

• $user->takeRole($role) You need to pass a role object to this method as the only one parameter it accepts in order to assign role to the user.

• $user->leaveRole($role) You need to pass a role object to this method as the only one parameter it accepts in order to deassign role from the user.

• $user->canAccess($subPermissionName) You need to pass a sub-permission name to this method as the only one parameter it accepts in order to check if the user have this specific sub-permission.

• $user->leaveAllRoles() This method don't accept any parameters and it just detach all roles related to the user.

• User::HasPermissions($permissionsIds) This is a query scope method in order to filter users whom have specific permissions and you can fetch the result as usual as using ->get(), ->first() or any other method as used to use.

note here that User model is used just as example and you can use the same functionality with any specified models in permissions.php config file after applying Mabrouk\Permission\Traits\HasPermission.php trait on it.

Attributes

• $user->roles return a collection of a user assigned roles.

• $user->permissions return a collection of a user assigned permissions.

• $user->subPermissions return a collection of a user assigned sub-permissions.

• $user->SubPermissionsNames return an array of a user assigned sub-permissions full names.

Out of the box models

We have 4 basic models to deal with:

• PermissionGroup have full crud with translatable name
• Permission ==> only index, show and update of translatable description and display name only. It depends on your project models names.
• SubPermission with no separate crud functionality. usually it's one of (view, create, edit, delete).
• Role have full crud with translatable name and description

Out of the box routes

Let's run the route:list command and discover our package predefined routes

php artisan route:list

Actually we will find the output of the following routes in addition to your project current routes:

Route::apiResource('permission-groups', PermissionGroupController::class);
Route::apiResource('permissions', PermissionController::class, ['except', ['store', 'destroy']]);
Route::apiResource('roles', RoleController::class);

Show, update and destroy routes accept model id as model segment in url

If above routes is not exists you may need to clear cached routes using command php artisan route:clear

What else?

You are one step away from handling your project permissions with only running below command after adding any additional routes under specified base urls defined in permissions.php config file.

Note:

You need to run below command after adding or modifying any routes related to base_urls you specified in config file in order to add or modify its suitable permissions.

php artisan permission:seed

Now you will find that specified project_full_permission_admins in config file have full permissions.

Sub Permissions will be added depending on your routes available actions. For example if you specified actions of api resource route to allow just store and destroy for example it will affect added sub permissions accordingly, otherwise it will add the 4 actions to super admin user to play with it according to specific role he is modifying.

Models Api Resources to expect in requests response

• PermissionGroupResource returned in all permission-groups requests except index

<?php

namespace Mabrouk\Permission\Http\Resources;

use Illuminate\Http\Resources\Json\JsonResource;

class PermissionGroupResource extends JsonResource
{
    /**
     * Transform the resource into an array.
     *
     * @param  \Illuminate\Http\Request  $request
     * @return array
     */
    public function toArray($request)
    {
        return [
            'id' => $this->id,
            'name' => $this->name,
            'permissions' => PermissionResource::collection($this->permissions),
        ];
    }
}

• PermissionGroupSimpleResource returned in permission-groups index request

<?php

namespace Mabrouk\Permission\Http\Resources;

use Illuminate\Http\Resources\Json\JsonResource;

class PermissionGroupSimpleResource extends JsonResource
{
    /**
     * Transform the resource into an array.
     *
     * @param  \Illuminate\Http\Request  $request
     * @return array
     */
    public function toArray($request)
    {
        return [
            'id' => $this->id,
            'name' => $this->name,
        ];
    }
}

• PermissionResource

<?php

namespace Mabrouk\Permission\Http\Resources;

use Illuminate\Http\Resources\Json\JsonResource;

class PermissionResource extends JsonResource
{
    /**
     * Transform the resource into an array.
     *
     * @param  \Illuminate\Http\Request  $request
     * @return array
     */
    public function toArray($request)
    {
        return [
            'id' => $this->id,
            'name' => $this->display_name,
            'selected' => $this->isSelected,
            'group' => new PermissionGroupSimpleResource($this->group),
            'sub_permissions' => SubPermissionResource::collection($this->subPermissions),
        ];
    }
}

• SubPermissionResource

<?php

namespace Mabrouk\Permission\Http\Resources;

use Illuminate\Http\Resources\Json\JsonResource;

class SubPermissionResource extends JsonResource
{
    /**
     * Transform the resource into an array.
     *
     * @param  \Illuminate\Http\Request  $request
     * @return array
     */
    public function toArray($request)
    {
        return [
            'id' => $this->id,
            'name' => $this->display_name,
            'selected' => $this->isSelected,
        ];
    }
}

• RoleResource ==> Used in role crud except index

<?php

namespace Mabrouk\Permission\Http\Resources;

use Mabrouk\Permission\Models\PermissionGroup;
use Illuminate\Http\Resources\Json\JsonResource;

class RoleResource extends JsonResource
{
    /**
     * Transform the resource into an array.
     *
     * @param  \Illuminate\Http\Request  $request
     * @return array
     */
    public function toArray($request)
    {
        return [
            'id' => $this->id,
            'name' => $this->name,
            'permission_groups' => PermissionGroupResource::collection(PermissionGroup::all()),
        ];
    }
}

• RoleSimpleResource ==> used in roles index only

<?php

namespace Mabrouk\Permission\Http\Resources;

use Illuminate\Http\Resources\Json\JsonResource;

class RoleSimpleResource extends JsonResource
{
    /**
     * Transform the resource into an array.
     *
     * @param  \Illuminate\Http\Request  $request
     * @return array
     */
    public function toArray($request)
    {
        return [
            'id' => $this->id,
            'name' => $this->name,
            'description' => $this->description,
        ];
    }
}

Any thing else?

Actually one more thing to know is that this package depend on mabrouk/translatable package in order to handle translation dynamically for any chosen language.

You will need to pass additional input "locale" in update requests of mentioned models and need to create roles and permission groups with your application default language. To get role/permission/permission group name or description with desired language you need to pass additional header to your requests "X-locale"

Both "locale" and "X-locale" accept values like ['en', 'ar', 'fr', ...] etc depending on languages you support in your project.

License

Mabrouk/Permission package is open-sourced software licensed under the MIT license.