Skip to main content

Hardware Catalog

Each platform offers its own list of hardware models. That per-platform list is what fills the hardware dropdown when an admin creates an account and orders devices. The catalog is built from a shared set of hardware models, but every platform decides which of those it actually offers.

The Hardware catalog card on a platform's detail page is where super-admins manage that list. It sits between the Device overrides and Zero Touch Provisioning cards and is collapsed by default — expand it to view or edit the catalog.

Seeding a platform's catalog

A platform that has never had its catalog set up shows an empty card with a Seed catalog button. Seeding copies every currently active hardware model into the platform's catalog, so the hardware dropdown stops coming up empty.

Seeding is safe to run more than once: it only adds models that are missing and never duplicates or resets anything you've already toggled. Use the Seed from templates button in the card header to pull in any models that were added after the platform was first seeded.

Turning models on and off

Each row in the table shows a model's manufacturer, model name, and device type, along with a Status badge and an Offered toggle:

  • Offered — the toggle controls whether this platform offers the model. Turning it off removes the model from the account-creation hardware dropdown without affecting any other platform.
  • Status reflects whether the model is actually available:
    • Offered — the model is on for this platform and available globally.
    • Off — the model is turned off for this platform.
    • Hidden (template off) — the model has been retired globally, so it is unavailable to every platform regardless of this platform's toggle. The Offered toggle is disabled in this state, and the per-platform setting is preserved, so the model reappears with its previous setting if it is brought back globally.

Notes

  • This surface is super-admin only. Platform admins cannot manage their own catalog yet.
  • Managing the shared, global list of models (adding new models or retiring them everywhere) is a separate, planned surface.