Skip to main content
IronKernel
Products Solutions For Customers About FAQ Contact
IronKernel Platform

Tower: Driver Context and Access Control

Provides controlled driver context, status visibility, and role-aware access across tower operations.

Problem

Provides controlled driver context, status visibility, and role-aware access across tower operations.

Capability

Provides controlled driver context, status visibility, and role-aware access across tower operations.

How it works

  1. 1 Global driver selector with search, status/location context, and truck assignment hints.
  2. 2 Driver selection synchronized with URL query state for deep-link continuity.
  3. 3 Role-based action gating for read-only versus action-capable users.
  4. 4 Consistent permission gate component used across mutation surfaces.

Operational outcomes

  • Global driver selector with search, status/location context, and truck assignment hints.
  • Driver selection synchronized with URL query state for deep-link continuity.
  • Role-based action gating for read-only versus action-capable users.

Integration boundaries

  • TMS (Primary Runtime Source)
  • CMMS (Embedded Health Context)
  • YMS (Task Execution Context)

Proof model

Feature-level proof

  • Driver Context and Access Control scope is defined in product module catalog.

    verified

    docs/products/tower/product.md · Module Catalog > Driver Context and Access Control

  • Tower driver oversight and cockpit workflows are implemented in dedicated portal pages and hooks.

    verified

    docs/products/tower/product.md · Module Catalog > Driver Cockpit Dashboard

    Code: frontend/apps/portal/src/products/tower/pages

    Contract: proto/tms/loads/v1

  • Tower oversight surfaces are implemented in portal product modules.

    verified

    docs/products/tower/product.md · Module Catalog > Load and Stop Oversight

    Code: frontend/apps/portal/src/products/tower

    Contract: proto/tms/loads/v1

Solution routes that reuse this feature

Open these solution and feature-map routes to test this behavior in end-to-end buyer workflows (0).

This feature is currently not linked to a named solution route. Review this behavior directly, then validate continuity through adjacent solution and feature-map routes.

Continuity routes for this capability

Route-level continuity checks where this feature appears in product-pair workflows.

This capability is currently mapped in adjacent solution and continuity routes. Browse linked solution routes first, then return here when cross-route continuity is expanded.