This chapter is for *programme owners and super-administrators* managing multiple race teams on one installation.

*Admin → Teams* lists every race programme on the platform. From here you can:

- Register a *new team* (identifier, display name, flags) - Assign *public hostname* for the team microsite where automation is enabled - Toggle programme capabilities (store, scrutineering, modules per team)

Team identifiers are used in URLs, card templates, and data scoping — choose stable short ids.

Issue *team passwords* or user records per your deployment policy. Map each login to:

- One *team id* - Optional *restricted modules* (subset of sidebar)

Document credentials through your secure channel — not in this wiki.

Before teams customise, set the *global default in Card studio* so new teams inherit a coherent BBM / Yardline baseline.

*Tracks catalogue* maintains circuit metadata and layout assets used when building logistics events (maps, labels). Refresh layout images on a schedule if your programme relies on Wikipedia-sourced diagrams.

*Membership billing configures plans and pricing when payment service integration is live. Until then, signups may be stored with free or demo* plan labels.

Super-admins do *not replace the championship’s sporting authority. Scrutineering, access control, and commercial terms with series owners remain contractual* outside the software.