@extends('layouts.app') @section('content')

Edit User Details

@csrf @method('PUT')

Designation, Branch & Unit

@csrf
PMO: Auto-assigns PMO role for Project workflow.
Head of Operation Division: Used for Project approval workflow.
Head of Corporate Division: Used for Asset approval workflow.
IT Department: Used for Asset approval workflow.
Finance: Automatically assigns Approver role.

Role Status

Approver Status
{{ $user->is_approver ? 'Yes' : 'No' }} @if($user->is_approver)
Can approve and reject all requests (final decision authority) @if($user->unit_id == 6)
Auto-assigned (Finance unit) @endif @else
Can only reject and approve & escalate requests @endif
PMO Status
{{ $user->isPMO() ? 'Yes' : 'No' }} @if($user->isPMO())
Special workflow rules for project requests @else
Standard workflow rules apply @endif

Approver Role

@if($user->unit_id == 6)
Finance Unit Auto-Assignment: Users in Finance unit are automatically assigned Approver role and cannot have it removed through this form. To change this user's approver status, first change their unit in the section above.
@endif
@csrf
is_approver ? 'checked' : '' }} {{ $user->unit_id == 6 ? 'disabled' : '' }}>
is_approver ? 'checked' : '' }} {{ $user->unit_id == 6 ? 'disabled' : '' }}>
All users except Approvers can reject and approve & escalate requests. Only users marked as "Approver" can make final approve/reject decisions.
Auto-Assignment: Users in Finance unit are automatically assigned Approver role.
Workflow Rules:
Asset: User → Others → IT Department → Head of Corporate → Approver
Project: User → Others → PMO → Head of Operations → Approver
Overwrite: User → Multiple Users → Approver
Special Roles: IT Department, PMO, Head divisions have specific escalation rules
Final Stage: Approvers cannot be bypassed and must make the final decision

Access Control Permissions

@csrf
Project Permissions
can_create_project ? 'checked' : '' }}>
can_view_project ? 'checked' : '' }}>
can_edit_project ? 'checked' : '' }}>
Users need at least one project permission to access the Project section.
{{-- Admin Control Privileges System --}}

Admin Control Privileges

Admin Control System: Grant users elevated privileges for system-wide request management. Choose the appropriate control level based on the user's responsibilities and role requirements.
@csrf
{{-- Option 1: View All Requests Only --}}
admin_control_level === 'view_only' ? 'checked' : '' }}>
✅ Permissions Granted:
  • View all requests system-wide (all departments, all users)
  • Access request details, attachments, and documents
  • View complete approval history and comments
  • Generate and export reports on any request
  • Search and filter across all requests
  • Download PDFs and attachments
  • View approval workflow and status
❌ Restrictions:
  • Cannot approve, reject, or escalate
  • Cannot add comments or take any action
  • Cannot edit request details
  • Cannot request resubmission
  • Read-only access to everything
Use Case: Auditors, compliance officers, staff members, or users from any role who need complete oversight without any decision-making power. Perfect for monitoring, reporting, and review purposes across all departments.
{{-- Option 2: Full Admin Control --}}
admin_control_level === 'full_control' ? 'checked' : '' }}>
✅ Permissions Granted:
  • Everything from "View All Requests"
  • Complete request management capabilities:
  • • Approve any request at any approval level
  • • Reject permanently with mandatory reason
  • • Reject & Request Resubmission - return to requester for corrections
  • • Escalate requests to higher authority
  • • Add comments and notes to any request
  • • View version comparisons for resubmitted requests
  • • Set resubmission deadlines
  • • Override normal approval workflows
  • • Approve requests from any department
  • • Full decision-making authority
❌ Restrictions:
  • Cannot delete requests permanently (data integrity)
  • Cannot modify other users' roles or permissions
  • Cannot access system configuration/settings pages
  • Cannot create/delete user accounts
Use Case: Senior staff, acting administrators, team leads, supervisors, or users from any role who need complete request management capabilities. This is the highest level of user privilege short of full system administrator access.
{{-- Option 3: No Admin Control (Default) --}}
admin_control_level === 'none' || !$user->admin_control_level ? 'checked' : '' }}>
Standard user permissions apply. User can only access requests they created or are assigned to approve based on their department and role.
@endsection