Pinrail Docs
TMS

Groups

Operator guidance for terminal groups, fleet membership, policy fanout, and group-level provisioning in TMS.

Overview

The TMS groups area is the operator workflow for managing a fleet of terminals as one operational unit.

Current Group Workflows

The current platform implementation supports these operator-facing workflows:

  • create and name terminal groups
  • assign or remove terminals from a group
  • review group membership and policy labels
  • apply routing-policy changes across a group
  • queue group-level command fanout
  • generate provisioning exports for a terminal fleet
  • review provisioning job history before applying, syncing, or rolling back a fleet change

The broader live platform surface includes:

  • GET /v1/terminal-groups
  • POST /v1/terminal-groups
  • group membership update routes under /v1/terminal-groups/{group_id}/terminals
  • group policy and routing routes under /v1/terminal-groups/{group_id}
  • group provisioning export and provisioning-job actions

Operational Guidance

Terminal groups should be treated as operator-owned rollout boundaries.

  • keep group membership intentional and reviewable
  • use group routing changes when the fleet should stay aligned on the same host or policy
  • generate exports from the target group before field distribution
  • use apply, sync, and rollback job history to trace fleet-wide provisioning actions later

On this page