# Freight TMS Admin Manual

## Purpose
This manual explains how a system administrator or company administrator controls the Freight TMS after installation.

## Core Admin Responsibilities
- Create and maintain companies, branches, and departments.
- Create users and assign department-wise roles.
- Control menu visibility and permission access.
- Maintain master data: currencies, tax rates, ports, airports, HS codes, container types, package types, document types, statuses, and numbering series.
- Monitor QA, health checks, backups, route/menu status, and schema consistency.
- Review audit logs, security events, API usage, notification logs, and workflow automation runs.

## Daily Admin Flow
1. Login as Platform Owner or Company Admin.
2. Review dashboard cards and system alerts.
3. Check pending users, support tickets, approvals, and exception center.
4. Confirm all active staff have correct branch, department, role, and menu access.
5. Review communication queue and failed notifications.
6. Review backup and health check status.

## User and Role Setup
- Create departments first.
- Create staff users under correct branch and department.
- Assign preset role such as Sales Manager, Pricing Staff, Operations Staff, Customs Staff, Warehouse Staff, Transport Staff, Finance Staff, Auditor, Driver, Customer Portal User, or Vendor Portal User.
- Use Role Access Matrix to verify permissions.
- Use Menu Manager to hide modules from roles that should not access them.

## Company Settings
Configure company branding, logo, invoice footer, numbering series, time zone, currency, tax settings, document templates, and email/SMS/WhatsApp provider settings before go-live.

## Security
- Use strong passwords.
- Activate MFA policy where available.
- Use IP allow/deny rules for corporate clients.
- Review active sessions and security incidents.
- Keep production APP_DEBUG=false.

## Backup
Before every upgrade or SQL patch:
- Export database from phpMyAdmin or server backup tool.
- Backup uploaded files from storage/app/public.
- Keep a copy of .env.

## Go-Live Checklist
- [ ] Company profile completed.
- [ ] Logo and branding uploaded.
- [ ] Roles and permissions verified.
- [ ] Numbering series configured.
- [ ] Mail settings tested.
- [ ] Backup tested.
- [ ] QA report clean.
- [ ] Demo data removed.
