Platform
A route or trip can be published through a read-only token and opened without a workspace session. The link can be revoked, while the internal load, settings, credentials and write controls remain behind authenticated access.
In the product
What changes
Each outcome connects what the software does to the decision a planner, loader or driver can actually make.
A token opens a deliberately limited public view of the shared route or trip. It does not create a team account or expose workspace navigation.
Screenshots go stale and invited accounts create access work. A bounded link keeps the recipient on the current published record.
The public link returns the shared operating view without edit, dispatch, credential or settings controls.
Hiding an edit button inside the normal application is not a sharing model. A separate read-only surface makes the boundary testable.
Revoking the share token removes public access while preserving the internal route and its audit record.
A forwarded PDF cannot be recalled. A revocable link gives operations a practical end to external access.
How it works
The logic is visible. There is no “AI decided” step between the load and the verdict.
Important boundary
A public link is intentionally limited and read-only. It is not a dispatch instruction, a permit, a certified scale result or an invitation to the carrier workspace.
Sharing starts from the internal record that operations already reviewed.
The server publishes only the fields allowed on the read-only surface.
The recipient opens it without joining the carrier workspace.
Public access ends without changing or deleting the internal plan.
Where to test it
Related capabilities
