Location Assignments¶
This guide explains how to assign team members to physical locations in your logistics pipeline. Location assignments determine which staff members are responsible for operations at each source depot, destination depot, and pickup point.
Prerequisites¶
- You are logged in as the organization owner or a manager with operations_flow write permission
- You have navigated to Config Hub > Country Operations > Operations Flow
- At least one depot or pickup point is configured for the selected country
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 vertical pipeline representing your logistics flow for the currently selected country.
Info
If you operate in multiple countries, use the country selector at the top of the Country Operations tab to switch between countries. The pipeline updates to show locations and assignments for the selected country.
Step 2: Identify the location node¶
The pipeline displays your configured locations as card nodes. Each location type appears at its position in the flow:
| Location Type | Pipeline Position | Description |
|---|---|---|
| Source Depot | Top of the pipeline | Your South African origin depot for the selected country |
| Destination Depot(s) | Below the Transporter node | All active destination depots in the selected country |
| Pickup Points | Bottom-left branch (after Dispatcher) | All active pickup points in the selected country |
Each node card shows the location name (or "Not configured" if missing) and any existing assignments as chips.
Step 3: Add an assignment¶
Tap the Add button on the location node where you want to assign a team member. A dialog appears with two fields:
- Member — A dropdown listing all members of your organization. Select the person to assign.
- Role — Choose the assignment role:
- Supervisor — Oversees operations at this location
- Officer — Handles day-to-day operations at this location
Tap Assign to confirm. The assignment immediately appears as a chip on the node.
Tip
You can assign multiple members to the same location. For example, a destination depot might have one supervisor and several officers handling different shifts.
Step 4: Review assignment chips¶
Each assignment displays as a chip on the location node showing:
- The team member's display name (or email if no name is set)
- Their assignment role in parentheses (e.g., "John Smith (Supervisor)")
Chips include a remove (×) button for users with write permission.
Step 5: Remove an assignment (if needed)¶
To remove an assignment, tap the × icon on the chip. The assignment is removed immediately — there is no confirmation dialog.
Warning
Removing an assignment is immediate. The team member loses their association with that location. You can re-assign them at any time using the Add button.
Visual Pipeline Layout¶
The Operations Flow screen shows the full logistics pipeline as a vertical flow with connectors between nodes:
┌─────────────────────┐
│ Source Depot │ ← Location assignments here
│ (SA origin) │
└─────────┬───────────┘
│
▼
┌─────────────────────┐
│ Transporter │ ← Route assignments (see Route Assignments guide)
│ │
└─────────┬───────────┘
│
▼
┌─────────────────────┐
│ Destination Depot(s) │ ← Location assignments here (per depot)
│ │
└─────────┬───────────┘
│
┌─────┴─────┐
▼ ▼
┌────────┐ ┌────────┐
│Dispatch│ │Drivers │ ← Route assignments
│ er │ │ │
└───┬────┘ └────────┘
│
▼
┌────────────────────┐
│ Pickup Points │ ← Location assignments here (per point)
│ │
└────────────────────┘
After the Destination Depot(s), the pipeline forks into two delivery paths:
- Left branch: Dispatcher → Pickup Points (batch delivery to collection locations)
- Right branch: Drivers (door-to-door delivery)
Note
The Transporter, Dispatcher, and Drivers nodes are route assignments, not location assignments. See Route Assignments for how to assign staff to those roles.
Result¶
After assigning a team member to a location:
- The assignment chip appears immediately on the relevant node in the pipeline
- The assigned member can be identified as responsible for that location in operational workflows
- Multiple members can be assigned to the same location with different roles (supervisor vs officer)
- Assignments persist across sessions and are visible to all team members who can view the Operations Flow screen
Troubleshooting¶
| Issue | Cause | Solution |
|---|---|---|
| Add button is not visible | You lack operations_flow write permission | Ask the organization owner to grant you write access to the operations_flow section. Owners always see the Add button. |
| Source Depot shows "Not configured" | No source depot has been set up for this country | Configure a source depot under Config Hub > Country Operations > Depots before assigning staff. |
| No destination depots appear | No active destination depots exist for the selected country | Add at least one destination depot with an active status in the Depots configuration. |
| No pickup points appear | No active pickup points exist for the selected country | Configure pickup points under Config Hub > Country Operations > Pickup Points. Only active pickup points appear on the pipeline. |
| Member dropdown is empty | No team members have been invited to the organization | Invite team members first via Config Hub > Organization > Team. See Inviting Members. |
| Cannot remove a chip | You lack operations_flow write permission | Only owners and managers with operations_flow write access can remove assignments. |
Related Guides¶
- Route Assignments — Assign staff to transport roles (transporter, dispatcher, driver)
- Operations — Overview of the full shipment operations workflow