Share roles

A share role is how an outside party (a carrier, a customer, an escort company, a permit service) gets access to a single load. Shares are scoped to one load at a time. The partner sees what you shared with them and nothing else about your business.

How to share a load

1. 1

   Open the load in Offload.

   Find the load you want to share and open its detail page.
2. 2

   Click "Share" on the load.

   Use the "Share" action on the load to start the sharing flow.
3. 3

   Pick the company or person you're sharing with (or invite a new one by email).

   Search your existing partners, or enter an email address to invite a new one.
4. 4

   Pick the share role from the seven options below.

   Choose the role that matches what the partner should be able to do (see the options below).
5. 5

   Send.

   Confirm to send the invitation. The partner gets an email to access this one load.

The partner gets an email and signs in to a partner-facing view of just that load.

Shares are per-load, not per-project. If you want a carrier to see five loads, you share each load with them. Project-level shares are not part of the model. This is intentional - it keeps the access boundary obvious to both sides.

Picking the right share role

If you're not sure, this table covers most cases:

Customer

Who it's for: the shipper or end customer whose cargo you're moving.

What they can do: read-only. They see the load: details, schedule, route, status, documents. They can't change anything.

Why read-only: the customer is the buyer of the haul. They want visibility (when does it arrive? where is it now?), not control. Anything they need to change, they ask you to do.

Carrier

Who it's for: another company actually hauling the load on your behalf. Used when you're the broker or the lead carrier handing off to a hauler.

What they can do: essentially a sub-dispatcher on this one load.

• Read and update load details (so they can correct dimensions, equipment, etc.)
• Manage equipment setup: assign their own trucks, trailers, and drivers to the load
• Manage permits and planned routes: pull permits, plan and edit the route
• Upload documents (proof of delivery, photos, BOLs)
• Propose a schedule change (request only - your dispatcher still approves the final schedule)

Why so much access: in heavy haul, the carrier hauling the load is doing the work. They need real authority over equipment and routing. Schedule stays in your hands so you can coordinate with the customer.

Sub-Hauler

Who it's for: a second-tier carrier supporting a multi-truck job. They're moving a piece of the load, not the whole thing.

What they can do:

• Read the load
• Update equipment setup (their assigned trucks, trailers, drivers)
• Propose a schedule change

The difference from Carrier: sub-haulers don't manage permits or routes. They show up, hook to their assigned setup, and run the route someone else planned.

Pilot / Escort

Who it's for: a pilot car or escort vehicle company.

What they can do: read-only on the load. They see the route, the schedule, the dimensions they're escorting, and the contact info. They don't change any of it.

Why read-only: escorts follow the plan. Schedule shifts, route changes, and permit amendments come through the dispatcher.

Route Surveyor

Who it's for: a surveyor scouting the route in advance for clearances, road conditions, and on-site issues.

What they can do:

• Read the load and route
• Create surveys on the load (upload survey notes, photos, measurements)

Why this role exists: route surveyors generate evidence (photos of low bridges, narrow turns, soft shoulders) that the dispatcher and driver use to finalize the route. They need a clean way to file the report without seeing or changing anything else.

Police / Utility / Railroad

Who it's for: a state trooper, utility coordinator, or railroad scheduler whose involvement is required by the permit.

What they can do: read-only. They see the load details and the route so they can confirm timing or coordinate on their end.

Permit Service

Who it's for: an outside permit-pulling service - the company that actually files for the state permits on your behalf.

What they can do:

• Read the load
• Manage permits on the load (scan permits, attach approval documents, update permit metadata)
• Upload documents
• Propose changes to permit route reviews (request only - your team reviews and approves)

The big difference from Carrier: Permit Service owns the permit. They don't touch equipment, schedule, or planned routes (apart from permit-driven route reviews). They're laser-focused on getting the paperwork right.

Quick comparison: share roles by capability

This is a snapshot. The full grid is on the Permission matrix page.

"Manage" includes read, edit, create, and delete. "Update" means edit but not delete or add new. "Create" means add new but not delete. "Yes" on read means they can see it; on a leaf row, it means they can do that thing.

Picking the right level

Start with the principle of least access:

• If they only need to see what's happening, use Customer, Pilot/Escort, or Police/Utility/Railroad depending on who they are.
• If they need to upload evidence (surveys, documents) but nothing else, use Route Surveyor.
• If they need to own a domain (permits, the route, the equipment), use Permit Service or Carrier.
• If they're helping but following someone else's plan, use Sub-Hauler.

If a partner doesn't fit any of these, talk to your Org Admin before inviting them as a regular org user. Inviting them as a Viewer gives them access to the entire org, which is almost never what you want.

Next: Permission matrix for the full grid, or "I want to..." Scenarios for goal-based lookup.