Partners and operating scope

Organizations own loads, transport partners and container moves. Each organization record has a name, code, active state, time zone and currency. The organization reference on a load and move is the operating context for the team. Transport partners have their own code, contact, address, active state and eligibility note, and belong to an organization. Selecting a partner on a load should refer to that maintained record rather than an unstructured name.

Team members connect named staff to the platform user identity and operating organization. Their active state, role name and time zone make the owner reference on a load meaningful. The user record carries email, role and account status. This structure supports ownership and scoped access during dispatch and review.

The App Administrator maintains organizations, team membership and partner records. Dispatchers use those records when preparing loads.

• Operating entity. Each load and terminal move points to an organization.
• Named person. A team member connects the work owner to a user account.
• Partner identity. The selected counterparty points to a maintained partner record.

Agree the organization codes and time zones before importing loads. A terminal team working across currencies should confirm which organization owns a load, because the load’s freight amount is stored in USD while the organization record also has a currency selection. Decide who may activate a partner and what the eligibility note must contain. Check whether a carrier and terminal operator should have separate partner records when they play different roles in the real movement.

Map every active team member to the correct user identity and organization. A change in staff responsibility should update the owner reference through the team’s controlled process. Rehearse a cross-organization case so a Dispatcher can verify the authorized owner and organization scope.

An administrator creates the operating organization with its code and time zone, then records a transport partner with a contact and eligibility note. The team member responsible for dispatch is tied to their user account. A Dispatcher preparing a load selects that organization, owner and partner. The load then has accountable people and counterparties that a supervisor can inspect without guessing from free text.

If the partner becomes inactive, the administrator keeps the historical partner record for existing loads and handles future selections under the organization’s procedure. The earlier load still points to the party that was chosen at the time. An Auditor can use the same relationships to follow the case from the load to the organization, owner and partner.

• Partner Directory — Partner identity, contact and organization context.
• My Team Member — The signed-in member’s identity and operating organization.
• Active Loads — Current work with the responsible owner and counterparty.

• Set up operating scope.
• Plan and dispatch a load.