Multi-Team Support for Freight Brokerages
ARK TMS now supports multi-team brokerage operations with team-scoped work, HQ oversight, user team assignments, and cleaner data separation.

ARK TMS now supports brokerages that operate across multiple offices, an HQ team, and freight agents under one brokerage. Teams can keep their own customers, loads, spot quotes, locations, billing views, and reports scoped to the people who should see them, while leadership can keep brokerage-wide visibility from the same system.
One Workspace for Offices, HQ, and Agents
Multi-team support gives freight brokerages one ARK workspace with team-level operating scopes. HQ can review the whole brokerage, office teams can focus on their freight, and agent teams can work under the broker without inheriting every other team's data.
| Load | Team | Customer | Lane | Status | Margin |
|---|---|---|---|---|---|
| #2482 | CHIChicago Office | Retail shipper | Chicago, IL -> Atlanta, GA | Needs coverage | $520 |
| #2481 | AGTAgent Network | Food shipper | Dallas, TX -> Denver, CO | Dispatched | $610 |
| #2479 | PHXPhoenix Office | Manufacturing shipper | Phoenix, AZ -> Salt Lake City, UT | Late risk | $465 |
| #2478 | HQHQ | Building materials | Toledo, OH -> Newark, NJ | Ready | $390 |
| #2477 | AGTAgent Network | Packaging shipper | Memphis, TN -> Charlotte, NC | On time | $440 |
The dashboard scope follows the operator into daily work. Load boards, spot quote views, customer lookups, lane history, billing, and reports use the selected team set so the same page can support one office, several offices, or full HQ oversight.
Data Separation Without Splitting the Brokerage
Freight agents and office users can be limited to the teams they are assigned to. A Chicago dispatcher can work Chicago freight, an agent can work agent-network freight, and an HQ manager can see all teams without switching accounts or creating duplicate brokerages.
This keeps shared brokerage operations intact while reducing accidental visibility across teams. Direct links, realtime load updates, exports, report filters, spot quote activity, and customer search all respect team access.
Admin Controls for Team Access
Admins can create teams, maintain team contact details, assign users to one or more teams, and choose each user's default team. Single-team brokerages keep the same workflow and do not see extra team controls.
For growing brokerages, this creates a cleaner path from one shared workspace to a multi-office or agent-supported operation. New users can start in the right team, create work in the right context, and expand access when their role changes.
Shared Customers Without Duplicate Records
Customers remain brokerage-level records, but their visibility can be mapped to the right teams. A customer can stay visible to one office, multiple offices, or HQ without copying the customer profile or fragmenting billing history.
That matters most when a brokerage serves the same shipper from multiple operating groups. ARK can keep one customer record while still making day-to-day work respect team boundaries.
Built for Brokerages That Are Adding Capacity
Multi-team support helps freight brokers add offices, agent teams, and specialized operating groups without rebuilding their TMS around each expansion. It is designed for the common brokerage growth model: central oversight, distributed operators, and clear separation between teams that should not see the same freight.
This release gives ARK customers more room to grow under one brokerage workspace.
