Invited customer guide

The right access for your part of the handoff.

Your organization assigns your role. Your sign-in keeps that access tied to you, and your facility scope keeps work in the right place.

How access works

Three checks. One personal account.

Use your own invited email and authenticator. Keep sign-in links, invitation codes, and authenticator setup keys private.

  1. 01

    Verify your identity

    Use the email address named in your invitation. An email sign-in confirms who you are; it does not choose your organization or role.

  2. 02

    Accept the assigned access

    Your organization sends a separate private invitation code. Confirm the intended organization with your administrator, then enter the code in the enabled customer interface.

  3. 03

    Choose your working context

    Select an available organization and, when needed, an assigned facility. Your current membership and permissions are checked for each action.

Common pilot roles

Match the role to the work.

These are role summaries, not a statement of your current access. Available actions also depend on membership, assigned scope, current authentication, and the approved pilot.

ORGANIZATION_OWNER

Organization owner

Accountable for organization administration and delegated access.

Can invite eligible roles within the organization’s access rules. Creating or transferring ownership uses a separate approved process; an ordinary invitation cannot grant ownership.

Ownership is never selected during sign-in.

LOGISTICS_MANAGER

Logistics manager

Coordinates loads, carriers, drivers, and equipment.

The role includes load planning and changes, carrier assignment, and release evaluation and review. It does not include issuing user invitations or issuing and redeeming release tokens.

Use this role for a logistics participant.

FACILITY_MANAGER

Facility manager

Works within specifically assigned facilities.

The role covers facility management, load operations, and security or release review within its assigned scope. It cannot issue organization invitations.

Facility scope must be assigned explicitly.

GATE_OPERATOR

Gate operator

Supports the gate workflow at an assigned facility.

This is a distinct facility role for gate activity, not general logistics administration. It cannot issue organization invitations. SHADOW participation never authorizes a real gate release.

Gate access is separate from logistics access.

Missing or incorrect access?

Ask the organization administrator who invited you to confirm the email, organization, role, and facility scope. If the role does not match your work, stop and have it corrected before continuing.