Administration and Controls
How administrators keep Logistic secure, configured, and reliable.
Access and Permissions
Start with least-privilege access. Give users only the permissions required for their actual responsibilities, then test using a non-admin account.
- delivery
- vehicle
- driver
Settings, Menus, and Configuration
Configuration files found
- default_menu.php
- menu.php
- module_config.php
- permissions.php
- routes.php
Menu entries found
- Logistics
- Submenu Lms Delivery
- Dispatch Board
- Submenu Lms Transfers
- Submenu Lms Vehicles
- Submenu Lms Drivers
- Odometer Logs
- Fuel Logs
- Vehicle Services
- Vehicle Contracts
- Locations
- Cost Analysis
- Vehicle Models
- Vehicle Brands
- Vehicle Categories
- Vehicle States
- Vehicle Tags
- Vehicle Service Types
Automation and Integrations
Scheduled jobs
1 job(s) found. Review cron, job setting gates, and last-run evidence.
Dashboard widgets
No dashboard widget registration was detected.
Public pages
No public page config or public-style route was detected.
API surfaces
Two read-only fleet surfaces, both module-owned since 1.1.0. The Integration API serves 6 endpoints under /api/v1/logistics (vehicles, deliveries, drivers) and is granted through the logistics:read OAuth scope. The End-User API serves the same 6 resources under /v1/api/logistics for the Syntry app, gated by the module_logistic tenant flag and then by the vehicle, delivery or driver permit. Routes are declared in config/api_routes.php and config/euapi_routes.php.
Seeders
Seeder files found: LogisticDemoSeeder.php. Use them only for the data purpose documented by the module.
Tests
One suite, run with php erpat module:test Logistic: LogisticApiTest guards both API surfaces — the controllers link against their base classes, the manifest and route sidecars agree, the module-flag and permit gates are present, and the endpoints stay out of core.
Administrative Controls Checklist
- The module toggle is enabled only for tenants or environments where the workflow is approved.
- Role permissions are assigned by responsibility, not by convenience.
- Menu entries, default menu entries, and routes point users to the intended module-owned screens.
- Users know who is allowed to change settings, templates, status rules, and delete actions.
- Migrations are applied and table changes are verified in the target tenant context.
Change Management
- Announce workflow or permission changes before they affect live users.
- Update module README, CHANGELOG, and this guide when a workflow changes.
- For menu, route, permission, widget, API, or migration changes, validate the module from a non-admin account.
- Keep public pages, API examples, dashboard widgets, and scheduled jobs aligned with the real data model.