Home · Platform · Core Functions
Enterprise ready

The Platform Layer Behind Every Agentic TMS Agent

Multi-tenancy, role-based access, and human-in-the-loop autonomy: the platform architecture that makes an Agentic TMS safe to run at enterprise scale.

Four Layers, One Accountable System

An Agentic TMS doesn’t earn enterprise trust through its agents alone. It earns it through what sits underneath them: who can see what, who approves what, how much an agent is allowed to do on its own, and whether every one of those decisions is provable after the fact. These are the four functions IT, security, and operations leadership look for before an agentic system touches production freight.

Multi-tenancy

Multi-Tenancy: One Platform, Fully Separated Workspaces

Agentic TMS is multi-tenant software by design: every customer, business unit, or regional office runs in its own isolated workspace, its own data, users, rates, carriers, and configuration, on shared infrastructure underneath. A workspace’s shipments, documents, and pricing are never visible outside it, and that isolation is enforced by the platform’s multi-tenant architecture itself, not by training or process.

For a forwarder running multiple offices, brands, or acquired entities on one instance, this multi-tenant SaaS security model is what keeps one branch’s rates invisible to another branch’s sales team without maintaining six separate logins or six separate systems.

Role-based access

Role-Based Access (RBAC): The Right Data for the Right Desk

Every user gets exactly the access their role requires and nothing more, role-based access control (RBAC) enforced automatically instead of left to convention. Sales sees rates and quotes. Operations sees bookings and milestones. Finance sees invoices and margin. TMS user permissions are defined once per role and applied everywhere an agent or a person touches the system, not left to whoever remembers to lock down a shared login or a shared inbox.

The same RBAC boundaries apply to agents, not just people. A pricing agent can quote a rate without ever seeing invoice data, and a customs agent can file an entry without touching a sales rep’s rate sheet.

Autonomy

Autonomy: How Much an Agent Does on Its Own, and Who Decides

Every agent in Agentic TMS runs inside an autonomy setting your team controls, per agent, per operation, Agentic TMS’s approach to human-in-the-loop AI and agent governance. The L1 to L5 model below sets exactly how much independence an agent has, from drafting a suggestion for a person to act on, to acting fully within policy with no case-by-case review.

LevelWhat the agent doesThe human’s role
L1Drafts a suggestion only, for example a quote or a customs field.Reviews and completes every action manually.
L2Prepares and stages the action, for example a filed entry or a sent quote.Approves before anything goes out (draft-and-approve mode).
L3Acts automatically on routine cases inside a defined threshold, for example quotes under a set margin variance.Reviews a digest; approves anything above the threshold.
L4Acts automatically across the workflow, escalating only what it flags.Intervenes only when an agent raises something.
L5Acts fully autonomously within policy.Audits the trail; no case-by-case review.

Most Agentic TMS customers start every agent at L1 or L2 in a Training sandbox, then raise autonomy workflow by workflow as trust builds, never as a single all-or-nothing switch, the same staged approach to autonomous AI agent oversight enterprise AI governance teams expect.

Digital mailroom

Digital Mailroom: Where Every Shipment Starts

Every inbound email, PDF, and attachment, across every channel and every tenant, is read, classified, and routed automatically before a person opens it, automated document routing that turns a bill of lading or an invoice into structured data without anyone typing it in by hand. That data lands in the right shipment and the right desk without anyone forwarding, saving to a shared drive, or manually filing a single document.

Digital Mailroom in Agentic TMS reading, classifying, and routing inbound documents automatically
Customs

PaperEntry AI: Customs

Customs entry automation is a core function of the platform, not an add-on. PaperEntry AI: Customs turns the documents behind a shipment into a validated, filed entry, and pulls a person in only when a check fails.

Accounts payable

PaperEntry AI: AP Invoice Automation

Alongside Digital Mailroom and Customs, the platform runs accounts payable end to end. PaperEntry AI reads supplier invoices, reconciles them against your purchase orders and receipts, and posts clean, approved payables into your finance system, so your team reviews exceptions instead of keying documents.

Frequently asked questions

Frequently Asked Questions

Is Agentic TMS multi-tenant?

Yes. Every customer, business unit, or office runs in its own isolated workspace, its own data, users, rates, and configuration, on shared infrastructure. No tenant can see another tenant’s shipments, documents, or pricing.

How does Agentic TMS handle role-based access control?

Permissions are defined per role, Sales, Operations, Finance, and enforced automatically for both people and agents. A user or an agent only ever sees the data and actions their role requires.

What is the L1 to L5 autonomy model?

It’s a five-level scale that sets how independently an agent can act, from L1 (drafts a suggestion only) to L5 (acts fully within policy, audited after the fact). Autonomy is set per agent, per operation, not platform-wide.

Can I control how much an AI agent is allowed to do on its own?

Yes. Every agent starts in a Training sandbox at a low autonomy level, typically L1 or L2, and autonomy is raised workflow by workflow as your team builds trust, never as a single switch for the whole platform.

Is there an audit trail for AI agent actions?

Every action any agent takes is logged, whether it was fully autonomous or required human approval, giving a complete, reviewable record per shipment and per tenant.
Ready when you are

See the Architecture Behind the Agents

Talk to our team about tenancy, access control, and how autonomy is governed in your environment. These are the agentic TMS architecture questions an enterprise TMS platform has to answer before your team ever touches a live shipment.