Your customer's dispatcher wants to see where the load is. Until now that meant somebody on your side creating an account for them, across a few unrelated screens, and answering by email every time another person at that company wanted in.
What changed
Creating a portal: name, address and the steps that follow, in one pass.
A portal is created through a wizard, from the customer it belongs to. Open a customer, create the portal there, and set member roles in the same pass. Each customer shows how much its portal is actually used, so you can tell a live account from one that was set up and forgotten.
Invitations land where they should. The invite email is readable, and its link identifies the invitation, so the recipient arrives at the right portal instead of a generic sign-in page.
Visitors can ask for access themselves. Someone who reaches your tracking page can request portal access, and the request queues for your staff to approve or reject. A company that would rather not review each one can turn on automatic approval.
You decide which shared links advertise the portal. The banner inviting recipients to request access is a per-share setting, so an external recipient only sees the invitation when that relationship calls for it.
Invites and requests live in one queue. Account staff send invitations and work through incoming requests in the same place, instead of tracking them across mailboxes.
Portal state is visible while you work an order. The customer box on an order shows whether that customer has portal access and lets you send an invite without leaving the screen.
Portal setup now sits under Settings, with the rest of the configuration.
