{"id":261,"date":"2025-08-27T16:40:24","date_gmt":"2025-08-27T16:40:24","guid":{"rendered":"https:\/\/1v0.net\/blog\/?p=261"},"modified":"2025-08-27T16:40:25","modified_gmt":"2025-08-27T16:40:25","slug":"creating-a-role-specific-dashboard-in-laravel-12","status":"publish","type":"post","link":"https:\/\/1v0.net\/blog\/creating-a-role-specific-dashboard-in-laravel-12\/","title":{"rendered":"Creating a Role-Specific Dashboard in Laravel 12"},"content":{"rendered":"\n

In many applications, different users need different dashboards. For example, an admin<\/strong> might see system statistics, a manager<\/strong> might see team performance, while a user<\/strong> only sees their own activity. In Laravel 12<\/strong>, you can create role-specific dashboards<\/strong> using the Spatie Permissions package and some conditional logic.<\/p>\n\n\n\n

In this guide, we\u2019ll build dashboards that automatically adapt based on the logged-in user\u2019s role. We\u2019ll secure routes, load different views, and provide a clean UI for each role.<\/p>\n\n\n\n

<\/div>\n\n\n\n

1 – Defining Roles<\/strong><\/h2>\n\n\n\n

Before building dashboards, make sure your roles are defined with Spatie Permissions<\/a>. For example:<\/p>\n\n\n

php<\/span> artisan<\/span> tinker<\/span>\n\n>>> Role<\/span>::create(<\/span>['name'<\/span> => 'admin'<\/span>]<\/span>);\n>>> Role<\/span>::create(<\/span>['name'<\/span> => 'manager'<\/span>]<\/span>);\n>>> Role<\/span>::create(<\/span>['name'<\/span> => 'user'<\/span>]<\/span>);<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
Assign roles to users when registering or via an admin UI. Example:<\/p>\n\n\n
$user->assignRole('admin'<\/span>);<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
<\/div>\n\n\n\n
2 – Route Setup<\/strong><\/h2>\n\n\n\n
We\u2019ll use a single dashboard route that points to a controller. Middleware ensures only authenticated users can access it.<\/p>\n\n\n
\/\/ routes\/web.php<\/span>\nuse<\/span> App<\/span>\\Http<\/span>\\Controllers<\/span>\\DashboardController<\/span>;\n\nRoute::middleware(['auth'<\/span>])->get('\/dashboard'<\/span>, [DashboardController::class, 'index'<\/span>])->name('dashboard'<\/span>);<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
<\/div>\n\n\n\n
3 – Dashboard Controller<\/strong><\/h2>\n\n\n\n
The controller checks the user\u2019s role and returns the correct view. This keeps logic centralized.<\/p>\n\n\n
\/\/ app\/Http\/Controllers\/DashboardController.php<\/span>\nnamespace<\/span> App<\/span>\\Http<\/span>\\Controllers<\/span>;\n\nuse<\/span> Illuminate<\/span>\\Support<\/span>\\Facades<\/span>\\Auth<\/span>;\n\nclass<\/span> DashboardController<\/span> extends<\/span> Controller<\/span>\n<\/span>{\n    public<\/span> function<\/span> index<\/span>()<\/span>\n    <\/span>{\n        $user = Auth::user();\n\n        if<\/span> ($user->hasRole('admin'<\/span>)) {\n            return<\/span> view('dashboards.admin'<\/span>);\n        }\n\n        if<\/span> ($user->hasRole('manager'<\/span>)) {\n            return<\/span> view('dashboards.manager'<\/span>);\n        }\n\n        return<\/span> view('dashboards.user'<\/span>);\n    }\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Now, each role gets its own dashboard view file.<\/p>\n\n\n\n
<\/div>\n\n\n\n
4 – Creating Dashboard Views<\/strong><\/h2>\n\n\n\n
Let\u2019s create separate views for each role:<\/p>\n\n\n
\/\/ resources\/views\/dashboards\/admin.blade.php\n@extends('layouts.app')\n\n@section('content')\n<div<\/span> class<\/span>=\"container\"<\/span>><\/span>\n  <h1<\/span>><\/span>Admin Dashboard<\/h1<\/span>><\/span>\n  <p<\/span>><\/span>System statistics and user management tools go here.<\/p<\/span>><\/span>\n<\/div<\/span>><\/span>\n@endsection<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n
\/\/ resources\/views\/dashboards\/manager.blade.php\n@extends('layouts.app')\n\n@section('content')\n<div<\/span> class<\/span>=\"container\"<\/span>><\/span>\n  <h1<\/span>><\/span>Manager Dashboard<\/h1<\/span>><\/span>\n  <p<\/span>><\/span>Team performance metrics and project controls go here.<\/p<\/span>><\/span>\n<\/div<\/span>><\/span>\n@endsection<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n
\/\/ resources\/views\/dashboards\/user.blade.php\n@extends('layouts.app')\n\n@section('content')\n<div<\/span> class<\/span>=\"container\"<\/span>><\/span>\n  <h1<\/span>><\/span>User Dashboard<\/h1<\/span>><\/span>\n  <p<\/span>><\/span>Your personal activity, notifications, and profile tools go here.<\/p<\/span>><\/span>\n<\/div<\/span>><\/span>\n@endsection<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
Each dashboard is independent, so you can customize the content for the needs of each role.<\/p>\n\n\n\n
<\/div>\n\n\n\n
5 – Securing Role-Specific Pages<\/strong><\/h2>\n\n\n\n
Sometimes you\u2019ll want to restrict not just dashboards but also subpages. You can use middleware or Blade directives for this.<\/p>\n\n\n
\/\/ Example: restrict reports route to managers<\/span>\nRoute::middleware(['auth'<\/span>,'role:manager'<\/span>])->get('\/reports'<\/span>, function<\/span> ()<\/span> <\/span>{\n    return<\/span> 'Reports Page'<\/span>;\n});<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n
\/\/ Example in Blade\n@role('admin')\n  <a<\/span> href<\/span>=\"\/admin\/settings\"<\/span>><\/span>Settings<\/a<\/span>><\/span>\n@endrole<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
This ensures that only users with the correct roles see links and access routes.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Wrapping Up<\/h2>\n\n\n\n
We created a role-specific dashboard system in Laravel 12<\/strong>. Each user sees a different dashboard based on their role, managed with Spatie Permissions. Routes are protected with middleware, and Blade directives ensure the right UI is displayed. This approach provides a tailored experience for each type of user while keeping security intact.<\/p>\n\n\n\n
<\/div>\n\n\n\n
What\u2019s Next<\/h2>\n\n\n\n