Trust, with clear boundaries

Know what protects the operating record.

We describe the access controls present in the product and separate them from production claims that require current operational evidence. That distinction matters when your loads, documents, and financial records live in one workspace.

Available in product

Logical company workspaces

Company records are scoped to the active workspace inside the shared application.

  • Active tenant membership checks
  • Tenant-scoped carrier routes
  • Workspace-aware navigation and data access

Boundary: This is logical application separation, not dedicated infrastructure per customer.

Available in product

Role-based team access

Team members receive roles and active memberships that control access to protected carrier workflows.

  • Role assignments
  • Write-role middleware
  • Active membership enforcement

Boundary: Customers should still review role assignments as their team changes.

Available in product

Focused driver access

Drivers work in a separate, assignment-aware experience instead of receiving access to the office TMS.

  • Driver activation flow
  • Assignment-scoped shipment access
  • Reassignment-aware authorization

Boundary: Driver access is delivered through a mobile-friendly web workspace today.

Available in product

Private shipment documents

Shipment paperwork is served through authenticated, authorized application routes.

  • Protected document routes
  • Tenant and assignment checks
  • Billing-readiness review states

Boundary: Public customer document links are not yet available.

Available in product

Reviewable activity history

Selected operational and administrative actions keep an audit history for accountability.

  • Assignment versions
  • Hold and override history
  • Paperwork and billing state history

Boundary: Audit coverage applies to selected important workflows, not every interaction in the application.

Available in product

Account and registration controls

Verified email and authenticated sessions protect access to company workflows.

  • Email verification
  • Authenticated application routes
  • Tenant membership validation

Boundary: No external security certification is claimed.

Operating responsibly

Application checks are not the same as production proof.

We use release checks to reduce avoidable deployment risk. Service-level, recovery, encryption, incident-response, and certification claims should only be published when the evidence is current and supportable.

Application operations control

Release and configuration checks

Automated checks help validate frontend releases and required production configuration before deployment.

  • Lint and type checks
  • Production build validation
  • Required environment checks

Boundary: Release checks reduce deployment risk but do not guarantee uninterrupted service.

Requires production evidence

Recovery evidence tracking

Operational readiness should be supported by current backup, restore-test, monitoring, and incident records.

  • Backup evidence
  • Restore-test evidence
  • Monitoring and incident records

Boundary: These claims require current production evidence before they are presented as customer commitments.

Questions about your operating requirements?

Bring us your access, workflow, or deployment questions and we will answer them against the product as it works today.

Talk with us