When several organizations work the same service areas — fleet partners, 3PL sub-fleets, or a mix of your own and external drivers — their managers should see the work that concerns them, and nothing that doesn’t. The platform now takes care of that automatically: from the moment a driver picks, claims, or is force-assigned a tour, the tour and its bookings are visible only to the driver’s own organization, which is also the only organization receiving their live updates and notifications. No information leaks between competing organizations while the work is on the road.

The rest of the lifecycle follows the same principle:

• When the driver leaves the tour again (ditch, unclaim, claim-window expiry, or revocation), the managing organizations regain visibility.
• A tour that completes or gets cancelled with a driver on it stays with the executing driver’s organization, also in history views — and the managing organizations you configured are no longer rewritten when a tour ends, so the list set via Update managing organizations stays what you set it to.
• Bookings split across several tours are visible to the organizations of all drivers currently executing them.
• Bookings and tours without managing organizations remain invisible to every organization manager while staying open to drivers of all organizations.

Previously, this behaviour required custom automation rewriting the managing organizations during the tour lifecycle; it is now the built-in default for every tenant, with no configuration needed.

Alongside this change we have thoroughly reworked the Booking & Tour Visibility documentation: it now walks through who sees what per role, the full lifecycle rules above, what carries over from bookings to tours on dispatch, and how related features — Linking Organizations to Service Areas, preferred drivers, and the gradual rollout extension — tie into visibility.