Create organizations and branches
After registering, you need to build an organization tree matching your real company structure. This is the foundation β every user, order, vehicle... belongs to a specific organization.

Conceptsβ
Road Freight TMS uses a multi-tenant tree model:
[Parent company]
ββ [Branch A]
β ββ [Depot A1]
β ββ [Depot A2]
ββ [Branch B]
ββ [Depot B1]
- Parent company = root, auto-created when you registered
- Branch = regional unit (HN, HCMC, DN...)
- Depot = physical unit with real coordinates, dispatch origin
When do you need branches & depots?β
| Scale | Recommended structure |
|---|---|
| One depot | Root + 1 depot β simplest |
| 2-3 depots in one city | Root + multiple peer depots |
| Multi-province | Root β Branch (per province) β Depot |
| Conglomerate | Root β Subsidiary β Branch β Depot |
Step 1: Open Administrationβ
Sidebar β "Administration" β "Organizations" tab.
Or use AI Agent: type "open organizations" β auto-navigates.
Step 2: Create a branchβ
Click "+ Add organization" in the top-right:
- Organization code (XCode): uppercase, no spaces β e.g.
CN-HN,CN-HCMC - Name (XName): display name β e.g.
HΓ Nα»i Branch - Type: choose "Branch"
- Parent: choose parent company (default if there's only one root)
Step 3: Create a depot (child of branch)β
Same as step 2 but:
- Type: choose "Depot"
- Parent: choose the branch just created
- Depot address: full (number, street, ward, district, province)
- Coordinates:
- Click "Auto-fetch coordinates from address" β calls OpenStreetMap
- OR open Google Maps β right-click the location β copy two numbers β paste
Depot coordinates are MANDATORY
The route optimizer uses depot coordinates as the start point. Wrong coordinates = wrong route. Verify on Google Maps before saving.
Editing the structure laterβ
After you have data (users, orders, vehicles), you can still:
- β Add new branches / depots
- β Edit name / address / coordinates
- β Cannot delete organizations with data
To delete β migrate data to another org first.
Permission inheritanceβ
After building the tree, when assigning a user to one branch:
User: Ms. B
Scope: HΓ Nα»i Branch
β
β Automatically sees: HN + all HN child depots
β Does NOT see: HCMC or other branches
See also: Role groups (RBAC).
Nextβ
- Role groups β Define permissions
- User management β Invite staff into the system