@extends('layouts.app') @section('title', 'Create Permission - ISP ERP System') @section('page-title', 'Create New Permission') @section('content')

Create New Permission

Add a new permission to the system

Permission Details

@csrf
@error('permission_key')
{{ $message }}
@enderror Use dot notation (e.g., users.create, users.edit, users.delete)
@error('menu_id')
{{ $message }}
@enderror Select a menu to associate with this permission. Type to search.
@error('parent_id')
{{ $message }}
@enderror Leave empty to create a root permission. Type to search.
@error('description')
{{ $message }}
@enderror
Inactive permissions cannot be assigned to users
Cancel
Naming Convention
Format: module.action

Use lowercase letters and dots to separate words

Examples:
  • users.create - Create users
  • users.edit - Edit users
  • users.delete - Delete users
  • clients.view - View clients
  • billing.manage - Manage billing
Best Practices:
  • • Keep keys short and descriptive
  • • Use consistent naming patterns
  • • Group related permissions
  • • Avoid special characters
Permission Hierarchy
Root Permissions

Top-level permissions that don't depend on others

Child Permissions

Sub-permissions that inherit from parent permissions

Tip: Use hierarchy to organize related permissions logically
@endsection @section('styles') @endsection @section('scripts') @endsection