Skip to main content

Overview

Larger operations and their customers—across rail, transload, intermodal, mobile, and more—need flexible permission structures for internal teams and external customers.⁠​​​‌​​​‌‌‌​​‌‌‌​‌​‌​‌‌​‌⁠ A single operator‑centric model is too rigid at scale.

Problem statement

In an operator‑centric model, users typically see everything within one operator.⁠​​​‌​​​‌‌‌​​‌‌‌​‌​‌​‌‌​‌⁠ For multi‑site or multi‑operator operations—or complex organizations—users need scoped access (by terminals, tracks/groups, workflows) and in some cases cross‑organization visibility. Example: because two operator codes exist, inventory appears separately and cannot be scoped cleanly without IAM.

Purpose

IAM provides a user‑defined, flexible way to manage access using identities (users, groups), roles (permissions), and policies (bindings with optional conditions).⁠​​​‌​​​‌‌‌​​‌‌‌​‌​‌​‌‌​‌⁠ It also enables a customer‑facing Portal through configuration rather than a separate system.

Get started

IAM Concepts

Understand the building blocks

Admin Portal

Manage IAM through the UI