Route Assignments¶
This guide covers how to assign team members to transport route roles on the Operations Flow pipeline. Route assignments designate who handles depot-to-depot transit, dispatch to pickup points, and door-to-door delivery.
Prerequisites¶
- You are logged in as the organization owner or a manager with
operations_flowwrite permission - You have navigated to Config Hub > Country Operations > Operations Flow
- At least one team member has been invited and accepted their invitation
Steps¶
Step 1: Open the Operations Flow screen¶
From the Config Hub, select the Country Operations tab and tap Operations Flow. The screen displays a visual pipeline showing the logistics flow for the currently selected country.
Info
If your courier operates in multiple countries, use the country dropdown at the top of the Country Operations tab to select the relevant country before opening Operations Flow.
Step 2: Locate the route node¶
The pipeline displays three route nodes at distinct positions:
| Route Role | Pipeline Position | Purpose |
|---|---|---|
| Transporter | Between Source Depot and Destination Depot(s) | Handles depot-to-depot transit |
| Dispatcher | Left fork, below Destination Depot(s) | Delivers batches from depot to pickup points |
| Driver | Right fork, below Destination Depot(s) | Handles door-to-door delivery |
The pipeline forks after the Destination Depot(s) node into two paths:
- Left path: Dispatcher → Pickup Points (batch collection)
- Right path: Drivers (door-to-door delivery)
Step 3: Tap Add on the route node¶
On the route node you want to assign a member to, tap the Add button. This opens the member selection dialog.
Tip
The Add button is only visible if you have write permission for the operations_flow section. If you don't see it, ask the organization owner to update your permissions.
Step 4: Select a team member¶
The assignment dialog presents two fields:
- Member — a dropdown listing all team members in the organization. Select the person you want to assign to this route.
- Role — choose either Supervisor or Officer to define their responsibility level on this route.
Info
This is the same member selection dialog used for Location Assignments. The interface is shared across all pipeline assignments.
Step 5: Confirm the assignment¶
Tap Assign to save. The assigned member appears as a chip on the route node, displaying their name and role label.
Country Scope¶
Route assignments are scoped to the currently selected country. When you add a route assignment:
- If a country is selected in the dropdown, the assignment is linked to that country
- If no country context is active, the assignment applies without a specific country scope
Note
Country scoping ensures that a team member assigned as a Transporter for one country does not automatically appear on another country's pipeline. Assign members per-country as needed.
Pipeline Layout Reference¶
The full Operations Flow pipeline displays the logistics chain from origin to delivery:
Source Depot
│
▼
Transporter
│
▼
Destination Depot(s)
│
├──────────┐
▼ ▼
Dispatcher Drivers
│
▼
Pickup Points
- Route nodes (Transporter, Dispatcher, Drivers) show assigned members as chips
- Location nodes (Source Depot, Destination Depots, Pickup Points) use location assignments instead — see Location Assignments
Removing a Route Assignment¶
To remove an existing assignment, tap the × on the member's chip. This requires owner access or operations_flow write permission.
Result¶
After assigning a member to a route:
- The member's name and role appear as a chip on the corresponding pipeline node
- The assignment is stored with optional country scope
- The member can now be identified as responsible for that route segment
- Multiple members can be assigned to the same route node (e.g., multiple transporters)
Troubleshooting¶
| Issue | Cause | Solution |
|---|---|---|
| Add button is not visible | You do not have operations_flow write permission |
Ask the organization owner to grant you write access, or ask the owner to make the assignment |
| Member dropdown is empty | No team members have accepted invitations | Invite team members first — see Inviting Members |
| Assignment not appearing on pipeline | Wrong country selected | Switch to the correct country in the country dropdown and verify the assignment |
| Cannot remove a chip | Insufficient permissions | Only owners and managers with operations_flow write access can remove assignments |
| Same member assigned twice | Duplicate assignment submitted | Remove the duplicate chip and re-assign if needed |
Related Guides¶
- Location Assignments — assigning members to physical locations (depots, pickup points)
- Roles & Permissions — managing the
operations_flowpermission section - Inviting Members — adding team members to your organization