Sub-Admin Systems

Lartrix supports creating independent sub-admin systems like merchant backend, agent backend, etc.

Create Sub-Admin

php artisan lartrix:make-backend Merchant \
    --path=/merchant \
    --api-prefix=api/merchant \
    --title="Merchant Admin"

Parameters:

Parameter	Description	Default
name	Module name	Required
--path	Frontend path	/
--api-prefix	API prefix	api/
--table	User table	{name}s
--title	Admin title	{name} Admin

Generated Structure

Modules/Merchant/
├── app/
│   ├── Http/Controllers/
│   │   ├── AuthController.php
│   │   ├── UserController.php
│   │   ├── RoleController.php
│   │   ├── MenuController.php
│   │   └── PermissionController.php
│   ├── Models/
│   │   └── Merchant.php
│   └── Providers/
├── config/
├── database/
│   ├── migrations/
│   └── seeders/
└── routes/api.php

Configure Authentication

Add to config/auth.php:

'guards' => [
    'merchant' => [
        'driver' => 'sanctum',
        'provider' => 'merchants',
    ],
],
'providers' => [
    'merchants' => [
        'driver' => 'eloquent',
        'model' => \Modules\Merchant\Models\Merchant::class,
    ],
],

Initialize Data

lartrix:make-backend runs the {Name}BackendSeeder automatically, creating:

• Default menus (home + system management)
• Permission data (four groups with children)
• Notification categories
• super-admin role (guard_name = merchant)
• admin / 123456 admin account

Note: do not use php artisan module:seed Merchant to initialize — nwidart's module:seed only recognizes {Name}DatabaseSeeder, while make-backend generates {Name}BackendSeeder, so module:seed will not run it.

Reinstall (New Database / New Environment)

When moving an existing sub-admin module to a new database, its migrations and Seeder are not re-run automatically. Use the reinstall command:

php artisan lartrix:backend-install Merchant

All steps are idempotent and safe to re-run:

1. Add the guard/provider to config/auth.php (skipped if present)
2. Enable the module and sync the modules table
3. Run module migrations (module:migrate, already-run ones are skipped)
4. Run the {Name}BackendSeeder data seeding
5. Print a summary (guard / path / admin credentials)

Data Isolation

Sub-admins isolate data by guard_name field:

// Menu isolation
Menu::where('guard_name', 'merchant')->get();

// Role isolation
Role::where('guard_name', 'merchant')->get();

// Permission isolation
Permission::where('guard_name', 'merchant')->get();

Add Business Features

Add business controllers in sub-admin:

<?php

namespace Modules\Merchant\Http\Controllers;

use Lartrix\Controllers\CrudController;

class ProductController extends CrudController
{
    protected function getModelClass(): string
    {
        return \Modules\Merchant\Models\Product::class;
    }

    protected function getResourceName(): string
    {
        return 'Product';
    }

    // Restrict to current merchant's data only
    protected function applyFilters($query, $request): void
    {
        $query->where('merchant_id', $request->user()->id);
    }
}

Access Sub-Admin

After starting the service, visit:

http://localhost:8000/merchant

Remove Sub-Admin

php artisan lartrix:remove-backend Merchant