Laravel RBAC Template

A scalable, production-ready Role-Based Access Control (RBAC) template built with Laravel 12. Designed to be easily integrated into any project with built-in Socialite authentication, activity logging, and a professional admin panel powered by Mazer.

Features

• Multi-Role System — Users can have multiple roles simultaneously
• Hierarchical Roles — Roles have levels (Super Admin > Admin > Manager > Editor > User)
• Module-based Permissions — Permissions grouped by module (e.g., users.create, posts.delete)
• Direct Permission Assignment — Assign permissions directly to users, bypassing roles
• Super Admin Bypass — Super admin role automatically bypasses all permission checks
• Policy-based Authorization — Laravel Policies integrated with RBAC permissions
• Socialite Integration — Pre-configured Google & GitHub login (easily extendable)
• Activity Log & Audit Trail — Track all changes with Spatie Activity Log
• Admin Panel — Professional admin UI with Mazer (Bootstrap 5)
• API Ready — Laravel Sanctum for token-based API authentication with RBAC middleware
• Caching — Built-in role/permission caching with automatic invalidation
• Blade Directives — @role, @permission, @superadmin directives
• Middleware — role:admin, permission:users.create route middleware
• Form Request Validation — Dedicated request classes for all admin operations
• Rate Limiting — Built-in throttle on authentication routes
• Feature Tests — Comprehensive test suite for roles, permissions, middleware, and API
• Artisan Commands — Quick setup with php artisan rbac:setup

Requirements

• PHP 8.2+
• Composer
• SQLite / MySQL / PostgreSQL
• Node.js (optional, for frontend asset compilation)

Quick Start

# Clone the repository
git clone https://github.com/zedlcompany/laravel-rbac.git
cd laravel-rbac

# Install dependencies
composer install

# Copy environment file
cp .env.example .env

# Generate application key
php artisan key:generate

# Run the RBAC setup (migrations + seeders + admin user)
php artisan rbac:setup

# Start the development server
php artisan serve

Default Admin Credentials:

• Email: admin@example.com
• Password: password

Configuration

All RBAC settings are in config/rbac.php:

return [
    'default_role' => 'user',
    'super_admin_role' => 'super-admin',

    'socialite' => [
        'enabled' => true,
        'default_role' => 'user',
        'auto_register' => true,
        'providers' => ['google', 'github'],
    ],

    'cache' => [
        'enabled' => true,
        'ttl' => 3600,
        'prefix' => 'rbac_',
    ],

    'activity_log' => [
        'enabled' => true,
        'log_name' => 'rbac',
    ],

    'admin' => [
        'prefix' => 'admin',
        'middleware' => ['web', 'auth', 'role:super-admin|admin'],
        'per_page' => 15,
    ],
];

Usage

Assigning Roles

// Assign a role
$user->assignRole('admin');
$user->assignRole('editor', 'manager');

// Remove a role
$user->removeRole('editor');

// Sync roles (replaces all existing)
$user->syncRoles(['admin', 'editor']);

// Check role
$user->hasRole('admin');           // true/false
$user->hasRole('admin|editor');    // has any
$user->hasAllRoles(['admin', 'editor']); // has all
$user->isSuperAdmin();             // true/false
$user->getRoleLevel();             // highest level (int)

Working with Permissions

// Give direct permission
$user->givePermission('users.create');

// Revoke permission
$user->revokePermission('users.create');

// Check permission (checks roles + direct)
$user->hasPermission('users.create');
$user->hasPermission('users.create|users.edit'); // has any
$user->hasAllPermissions(['users.create', 'users.edit']);

// Get all permissions
$user->getAllPermissions();
$user->getPermissionsByModule();

Role Permissions

// Assign permissions to a role
$role = Role::where('slug', 'editor')->first();
$role->givePermission('posts.create', 'posts.edit');
$role->syncPermissions(['posts.create', 'posts.edit', 'posts.delete']);
$role->revokePermission('posts.delete');

Middleware

// In routes
Route::middleware('role:admin')->group(function () {
    // Only admin can access
});

Route::middleware('permission:users.create')->group(function () {
    // Only users with 'users.create' permission
});

Route::middleware('role:admin|manager')->group(function () {
    // Admin OR Manager can access
});

Blade Directives

@role('admin')
    <p>You are an admin!</p>
@endrole

@permission('users.create')
    <a href="/users/create">Create User</a>
@endpermission

@superadmin
    <p>Full system access</p>
@endsuperadmin

@anyrole(['admin', 'manager'])
    <p>Admin or Manager content</p>
@endanyrole

Policies

The template includes Laravel Policies that integrate with the RBAC system:

// In controllers
$this->authorize('viewAny', User::class);
$this->authorize('update', $user);
$this->authorize('delete', $role);

// In Blade
@can('update', $user)
    <a href="{{ route('admin.users.edit', $user) }}">Edit</a>
@endcan

// Super admin automatically bypasses all policy checks via Gate::before()

Contracts/Interfaces

The template provides interfaces for type-hinting:

use App\Contracts\HasRolesInterface;
use App\Contracts\HasPermissionsInterface;

// Your User model implements both
class User extends Authenticatable implements HasRolesInterface, HasPermissionsInterface
{
    use HasRoles, HasPermissions;
}

API Authentication

This template includes Laravel Sanctum with RBAC-protected API routes:

# Available API endpoints (requires Bearer token)
GET /api/user              # Current user profile with roles
GET /api/user/permissions  # User's permissions and roles list

# Admin API (requires admin role)
GET /api/admin/users       # List users (paginated)
GET /api/admin/roles       # List roles with permissions
GET /api/admin/permissions # List permissions grouped by module

// Create a token
$token = $user->createToken('api-token')->plainTextToken;

// Use in requests
Authorization: Bearer {token}

Socialite Setup

Google

1. Create OAuth credentials at Google Cloud Console
2. Add to .env:

GOOGLE_CLIENT_ID=your-client-id
GOOGLE_CLIENT_SECRET=your-client-secret
GOOGLE_REDIRECT_URI=${APP_URL}/auth/google/callback

GitHub

1. Create OAuth App at GitHub Developer Settings
2. Add to .env:

GITHUB_CLIENT_ID=your-client-id
GITHUB_CLIENT_SECRET=your-client-secret
GITHUB_REDIRECT_URI=${APP_URL}/auth/github/callback

Adding More Providers

1. Add the provider to config/rbac.php:

'socialite' => [
    'providers' => ['google', 'github', 'facebook'],
],

1. Add credentials to config/services.php:

'facebook' => [
    'client_id' => env('FACEBOOK_CLIENT_ID'),
    'client_secret' => env('FACEBOOK_CLIENT_SECRET'),
    'redirect' => env('FACEBOOK_REDIRECT_URI'),
],

1. Install the provider package if needed.

Login URLs

GET /auth/google/redirect   → Redirects to Google
GET /auth/google/callback   → Handles callback
GET /auth/github/redirect   → Redirects to GitHub
GET /auth/github/callback   → Handles callback

Admin Panel

Access the admin panel at /admin (requires super-admin or admin role).

The admin panel uses Mazer — a free Bootstrap 5 admin dashboard template with:

• Responsive sidebar navigation
• Dark mode support
• Clean card-based layouts
• Bootstrap Icons

Features:

• Dashboard — Overview stats and recent activity
• Users — CRUD, role assignment, search & filter
• Roles — CRUD, permission assignment, hierarchical levels
• Permissions — CRUD, module-based grouping
• Activity Log — Full audit trail with filtering

Architecture

app/
├── Console/Commands/RbacSetup.php      # Setup artisan command
├── Contracts/                          # Interfaces
│   ├── HasPermissionsInterface.php
│   └── HasRolesInterface.php
├── Http/
│   ├── Controllers/
│   │   ├── Admin/                      # Admin CRUD controllers
│   │   └── Auth/                       # Auth + Socialite controllers
│   ├── Middleware/
│   │   ├── CheckPermission.php
│   │   └── CheckRole.php
│   └── Requests/Admin/                 # Form Request validation
├── Models/
│   ├── Permission.php
│   ├── Role.php
│   └── User.php
├── Observers/RoleObserver.php          # Cache invalidation
├── Policies/                           # Authorization policies
│   ├── PermissionPolicy.php
│   ├── RolePolicy.php
│   └── UserPolicy.php
├── Providers/RbacServiceProvider.php   # Middleware, policies, directives
└── Traits/
    ├── HasPermissions.php
    └── HasRoles.php

Database Structure

users
├── id, name, email, password, avatar, provider, provider_id
├── email_verified_at, remember_token, timestamps

roles
├── id, name, slug, description, level, is_active, timestamps

permissions
├── id, name, slug, description, module, timestamps

role_user (pivot)
├── id, role_id, user_id, timestamps

permission_role (pivot)
├── id, permission_id, role_id, timestamps

permission_user (pivot)
├── id, permission_id, user_id, timestamps

activity_log (spatie)
├── id, log_name, description, subject_type, subject_id
├── causer_type, causer_id, properties, event, batch_uuid, timestamps

Default Roles

Artisan Commands

# Full setup (migrations + seeds + admin user)
php artisan rbac:setup

# Fresh setup (drops all tables first)
php artisan rbac:setup --fresh

# Custom admin credentials
php artisan rbac:setup --admin-email=admin@myapp.com --admin-password=secret123

Testing

# Run all tests
php artisan test

# Run specific test files
php artisan test --filter=RoleTest
php artisan test --filter=PermissionTest
php artisan test --filter=MiddlewareTest
php artisan test --filter=ApiAuthTest

Test Coverage:

• RoleTest — Role assignment, removal, sync, pipe-separator check, level, inactive roles
• PermissionTest — Direct permissions, role permissions, super admin bypass, module grouping
• MiddlewareTest — Role/permission middleware blocking, guest redirect, throttle
• ApiAuthTest — Sanctum authentication, admin API access control

Extending

Adding New Permissions

Add to database/seeders/PermissionSeeder.php:

['name' => 'Create Posts', 'slug' => 'posts.create', 'module' => 'posts', 'description' => 'Create new posts'],
['name' => 'Edit Posts', 'slug' => 'posts.edit', 'module' => 'posts', 'description' => 'Edit existing posts'],

Then run: php artisan db:seed --class=PermissionSeeder

Adding New Roles

Add to database/seeders/RoleSeeder.php:

[
    'name' => 'Content Manager',
    'slug' => 'content-manager',
    'description' => 'Manages all content',
    'level' => 50,
    'is_active' => true,
],

Custom Middleware

You can combine roles and permissions:

Route::middleware(['auth', 'role:admin', 'permission:users.create'])->group(function () {
    // Must be admin AND have users.create permission
});

Cache Invalidation

Cache is automatically invalidated when:

• A user's roles are changed (assignRole, removeRole, syncRoles)
• A user's direct permissions are changed (givePermission, revokePermission)
• A role is updated or deleted (via RoleObserver)
• A role's permissions are synced (via RoleObserver::clearCacheForRole())

Tech Stack

• Laravel 12 — PHP Framework
• Mazer — Bootstrap 5 Admin Dashboard (admin panel)
• Tailwind CSS — Utility-first CSS (frontend/public pages via Vite)
• Laravel Socialite — Social authentication
• Laravel Sanctum — API authentication
• Spatie Activity Log — Audit trail
• PHPUnit — Testing framework

Contributing

1. Fork the repository
2. Create your feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

License

This project is open-sourced software licensed under the MIT license.