epigra / nova-permissions
Laravel Nova Grouped Permissions.
Requires
- php: >=7.2.0
- spatie/laravel-permission: 3.*
- dev-master
- 1.0.6
- 1.0.5
- 1.0.4
- 1.0.3
- 1.0.2
- 1.0.1
- 1.0.0
- dev-dependabot/npm_and_yarn/url-parse-1.5.3
- dev-dependabot/npm_and_yarn/path-parse-1.0.7
- dev-dependabot/npm_and_yarn/dns-packet-1.3.4
- dev-dependabot/npm_and_yarn/hosted-git-info-2.8.9
- dev-dependabot/npm_and_yarn/lodash-4.17.21
- dev-dependabot/npm_and_yarn/y18n-3.2.2
- dev-dependabot/npm_and_yarn/elliptic-6.5.4
- dev-dependabot/npm_and_yarn/ini-1.3.7
- dev-dependabot/npm_and_yarn/http-proxy-1.18.1
- dev-dependabot/npm_and_yarn/node-sass-4.14.1
- dev-dependabot/npm_and_yarn/websocket-extensions-0.1.4
This package is not auto-updated.
Last update: 2024-11-03 15:18:20 UTC
README
A Laravel Nova Tool that allows you to group your Permissions into Groups and attach it to Users. It uses Spatie's laravel-permission.
We have a Migration, Seed, Policy and Resource ready for a good Authorization Experience.
Installation
You can install the package in to a Laravel app that uses Nova via composer:
composer require eminiarts/nova-permissions
Publish the Migration with the following command:
php artisan vendor:publish --provider="Eminiarts\NovaPermissions\ToolServiceProvider" --tag="migrations"
Migrate the Database:
php artisan migrate
Next up, you must register the tool with Nova. This is typically done in the tools
method of the NovaServiceProvider
.
// in app/Providers/NovaServiceProvider.php // ... public function tools() { return [ // ... new \Eminiarts\NovaPermissions\NovaPermissions(), ]; }
If you want to hide the tool from certain users, you can write your custom logic for the ability to see the tool:
// in app/Providers/NovaServiceProvider.php // ... public function tools() { return [ // ... (new \Eminiarts\NovaPermissions\NovaPermissions())->canSee(function ($request) { return $request->user()->isSuperAdmin(); }), ]; }
Finally, add MorphToMany
fields to you app/Nova/User
resource:
// ... use Laravel\Nova\Fields\MorphToMany; public function fields(Request $request) { return [ // ... MorphToMany::make('Roles', 'roles', \Eminiarts\NovaPermissions\Nova\Role::class), MorphToMany::make('Permissions', 'permissions', \Eminiarts\NovaPermissions\Nova\Permission::class), ]; }
Add the Spatie\Permission\Traits\HasRoles trait to your User model(s):
use Illuminate\Foundation\Auth\User as Authenticatable; use Spatie\Permission\Traits\HasRoles; class User extends Authenticatable { use HasRoles; // ... }
A new menu item called Permissions & Roles will appear in your Nova app after installing this package.
Permissions with Groups
Detail View
Edit View
Database Seeding
Publish our Seeder with the following command:
php artisan vendor:publish --provider="Eminiarts\NovaPermissions\ToolServiceProvider" --tag="seeds"
This is just an example on how you could seed your Database with Roles and Permissions. Modify RolesAndPermissionsSeeder.php
in database/seeds
. List all your Models you want to have Permissions for in the $collection
Array and change the email for the Super-Admin:
<?php use Illuminate\Database\Seeder; use Spatie\Permission\Models\Role; use Spatie\Permission\Models\Permission; class RolesAndPermissionsSeeder extends Seeder { /** * Run the database seeds. * * @return void */ public function run() { // Reset cached roles and permissions app()[\Spatie\Permission\PermissionRegistrar::class]->forgetCachedPermissions(); $collection = collect([ 'invoices', 'clients', 'contacts', 'payments', 'teams', 'users', 'roles', // ... your own models/permission you want to crate ]); $collection->each(function ($item, $key) { // create permissions for each collection item Permission::create(['group' => $item, 'name' => 'view ' . $item]); Permission::create(['group' => $item, 'name' => 'view own ' . $item]); Permission::create(['group' => $item, 'name' => 'manage ' . $item]); Permission::create(['group' => $item, 'name' => 'manage own ' . $item]); Permission::create(['group' => $item, 'name' => 'restore ' . $item]); Permission::create(['group' => $item, 'name' => 'forceDelete ' . $item]); }); // Create a Super-Admin Role and assign all permissions to it $role = Role::create(['name' => 'super-admin']); $role->givePermissionTo(Permission::all()); // Give User Super-Admin Role $user = App\User::whereEmail('your@email.com')->first(); // enter your email here $user->assignRole('super-admin'); } }
Now you can seed the Database. Add $this->call(RolesAndPermissionsSeeder::class);
to the DatabaseSeeder
.
Note: If this doesn't work, run
composer dumpautoload
to autoload the Seeder.
Create a Model Policy
You can extend Eminiarts\NovaPermissions\Policies\Policy
and have a very clean Model Policy that works with Nova.
For Example: Create a new Contact Policy with php artisan make:policy ContactPolicy
with the following code:
<?php namespace App\Policies; use Eminiarts\NovaPermissions\Policies\Policy; class ContactPolicy extends Policy { /** * The Permission key the Policy corresponds to. * * @var string */ public static $key = 'contacts'; }
It should now work as exptected. Just create a Role, modify its Permissions and the Policy should take care of the rest.
Note: Don't forget to add your Policy to your
$policies
inApp\Providers\AuthServiceProvider
.
Note: Only extend the Policy if you have created your Permissions according to our Seeding Example. Otherwise, make sure to have
view contacts, view own contacts, manage contacts, manage own contacts, restore contacts, forceDelete contacts
as Permissions in your Table in order to extend our Policy.
view own contacts
is superior toview contacts
and allows the User to only view his own Contacts.
manage own contacts
is superior tomanage contacts
and allows the User to only manage his own Contacts.
Super Admin
A Super Admin can do everything. If you extend our Policy, make sure to add a isSuperAdmin()
Function to your App\User
Model:
<?php namespace App; class User { /** * Determines if the User is a Super admin * @return null */ public function isSuperAdmin() { return $this->hasRole('super-admin'); } }
You can modify this function as you please.
Scope Resource for User
If you use our Policy and Seeder, the user will still be able to see other Entries. In order to only allow a User to view his own Entries and no others, you can extens our Eminiarts\NovaPermissions\Nova\ResourceForUser
Class like this:
<?php namespace App\Nova; use Eminiarts\NovaPermissions\Nova\ResourceForUser; class Contact extends ResourceForUser { //... }
Note: ResourceForUser assumes the Resource has a
user_id
column in the Database. If you are using another column, feel free to copy the contents of the Resource and modify it.
Customization
Use your own Resources
If you want to use your own resource classes, you can define them when you register the tool:
// in app/Providers/NovaServiceProvider.php // ... use App\Nova\Role; use App\Nova\Permission; public function tools() { return [ // ... \Eminiarts\NovaPermissions\NovaPermissionTool::make() ->roleResource(Role::class) ->permissionResource(Permission::class), ]; }
Credits
This Package is inspired by vyuldashev/nova-permission and silvanite/novatoolpermissions. I wanted to have a combination of both. Thanks to both authors. Also, a huge thanks goes to Spatie spatie/laravel-permission for their amazing work!