Logistic Reference Public

Getting Started

A practical first-run checklist for enabling Logistic, granting the right permissions, preparing your starter data, and training the first users.

Guide version: r1 Module version: 1.0.0 Updated: 2026-07-22 Estimated time: 2 min 1 views
Start Here

Getting Started

A practical first-run checklist for enabling Logistic, preparing access, and training the first users.

Slug: logisticVersion: 1.0.0Category: DistributionReviewed: 2026-07-11

Before You Begin

  • A working ERPat tenant or main database with the module installed.
  • Administrator access for first setup and a non-admin test account for validation.
  • A named business owner who can approve statuses, labels, templates, and reports.
  • Module migrations should be applied before live users create records.

First-Run Setup Checklist

  • Confirm the module is enabled in Settings > Manage Modules and that the sidebar item appears for an administrator.
  • Review the module purpose with the owner of the workflow before users start entering real records.
  • Assign role permissions for create, update, delete, settings, reports, and any special management actions.
  • Open the first screen from the left menu and confirm list pages, modal forms, and detail pages load without warnings.
  • Create or verify starter records such as categories, statuses, templates, locations, teams, or settings that the workflow depends on.
  • Run a small end-to-end sample using a non-critical record, then confirm the expected report, dashboard, public page, or downstream handoff updates.
  • Use the module seeder only for demo or sample data, and review the generated rows before using them for live operations.

Starter Data to Prepare

Core records

  • vehicles
  • deliveries

Configuration records

  • Role permissions for delivery, vehicle, driver.
  • Sidebar and default menu placement for Logistics, Submenu Lms Delivery, Dispatch Board, Submenu Lms Transfers, Submenu Lms Vehicles.

Training Path for New Users

  1. Explain the purpose of the module and what business process it controls.
  2. Show the main list or dashboard and identify the columns, filters, and action buttons users will touch daily.
  3. Create one sample record together, then edit it, review it, and complete the expected next action.
  4. Show where the record appears in reports, related modules, or public/customer-facing pages.
  5. Review what users should not change without manager approval, especially settings, templates, permissions, and delete actions.
Was this guide helpful?

Report a content problem