49 Reports, SMS & Setup
Setup
Company profile, setup center, access control, branches, tax, and configuration tools.
Illustrations on this page are conceptual examples — not screenshots of the live system.
How you can use it
The same Fleet module supports different transport models — pick the scenarios that match your operation.
Setup in daily operations
Company profile, setup center, access control, branches, tax, and configuration tools.
Platform administration
Setup for system administrators — typical in Bangladesh multi-branch VMS rollouts.
Module enable/disable per company or…
Teams use Setup when they need module enable/disable per company or branch — without maintaining a separate spreadsheet or WhatsApp thread.
Role templates and permission bundles
Teams use Setup when they need role templates and permission bundles — without maintaining a separate spreadsheet or WhatsApp thread.
Benefits for your team
What improves when vehicle data lives in one place instead of spreadsheets and phone calls.
Module enable/disable per company or…
Setup helps because module enable/disable per company or branch — recorded inside the VMS audit trail instead of informal channels.
Role templates and permission bundles
Setup helps because role templates and permission bundles — recorded inside the VMS audit trail instead of informal channels.
Integration hooks and system parameters
Setup helps because integration hooks and system parameters — recorded inside the VMS audit trail instead of informal channels.
Company branding and operational defaults
Setup helps because company branding and operational defaults — recorded inside the VMS audit trail instead of informal channels.
Makes daily work easier
Less chasing, less re-entry, fewer surprises on the morning dispatch board.
- Setup supports view, add, settings — so users do not jump between unrelated tools for the same task.
- Less manual follow-up: module enable/disable per company or branch
- Less manual follow-up: role templates and permission bundles
- Less manual follow-up: integration hooks and system parameters
- Branch-scoped access means local teams open Setup without seeing other depots' records.
Multi-user & mobile-ready
Different roles see different slices — desktop for planning, mobile for field, dashboard for leadership.
- Operations lead (desktop)Plans and supervises Setup with full register access, filters, and exports.
- Branch user (tablet / laptop)Works on branch-scoped Setup records — no cross-branch data leakage.
- Field staff (mobile)Submits or confirms Setup tasks from phone — limited permissions, faster updates.
- Manager / approverReviews exceptions, approvals, and summaries inside Setup without re-keying data.
- Owner / executive (dashboard)Reads KPI widgets fed by Setup — not day-to-day data entry screens.
Works with your other modules
Fleet is the vehicle master — other modules read from it so data stays consistent across the platform.