Orbit Hub: Links, Flows & Access
Which Orbit Hub links exist (Hub login, public and authenticated flows), who each one is for, and why a Hub root address can return a 404.
Which Orbit Hub links exist (Hub login, public and authenticated flows), who each one is for, and why a Hub root address can return a 404.
Was this article helpful?
Did not find your answer?
Ask Luna, or write to our support team.
Note
Orbit Hub is the app for Shippers. This article explains which Hub links exist and who each one is for.
Every Orbit Hub lives on its own address, for example https://your-hub.shop.orbit.do. Which pages exist behind that address is decided by the Hub's flow configuration in Orbit MissionControl under Settings → Hubs → your Hub → Flow Configuration. Orbit MissionControl lists every resulting link on the same page and on Settings → General, each with a copy and an open button.
Key highlights
https://your-hub.shop.orbit.do/portal/login./portal/.| Audience | Link | Where to find it |
|---|---|---|
| Shippers who have an account (or whom you invite) | Hub login — …/portal/login | Settings → General (Hub card) or the Hub settings header |
| Website visitors, prospects, anyone without an account | A public flow — …/ or …/<slug> | Hub settings header → "Show all Hub links", or the flow row itself |
| Your own website | Calculator widget embed | Hub settings → Calculator Widget |
A public flow is a booking page that anyone can open. Its address is the Hub address plus the flow's URL slug: a flow with the slug express is reachable at https://your-hub.shop.orbit.do/express. Leave the slug empty to serve the flow at the root address. A public flow can additionally enable sign-up, so that a first-time customer books and creates an account in one go.
Authenticated flows appear in the sidebar of the Hub after login and are reachable at https://your-hub.shop.orbit.do/portal/<slug>. They can be restricted to specific Shippers through a shipper query. One authenticated flow is the target of the "Book transport" button on the Hub home screen — by default the flow with the slug book, or the slug you enter as the booking flow slug in the flow configuration.
The root address https://your-hub.shop.orbit.do/ only serves a page when a public flow with an empty slug exists. If your Hub has no flows at all, or only flows with a slug, the root address returns "not found". Orbit MissionControl shows this state as an amber "No booking flow configured" indicator. Add a public flow with an empty slug, or share the Hub login or a specific flow link instead.
Julia runs a courier company in Lyon. Her Hub https://lyon-express.shop.orbit.do has two public flows — one at the root for same-day parcels, one at /pallets — and an authenticated flow book for contract customers. She puts the root link and the calculator widget on her website, sends new contract customers the Hub login link, and her account managers copy the /pallets link into quotes for prospects.
Yes. Edit the flow in the flow configuration; the old address stops working immediately, so update any place you shared it.
The standalone sign-up page under /signup is only available while standalone sign-up is enabled for the Hub and is being phased out. Prefer a public flow with sign-up enabled.
Each Hub has its own address and its own flow configuration. Settings → General in Orbit MissionControl lists every Hub with its login link and flow summary.
No. It means at least one booking flow exists. It does not monitor uptime.