Device Config

Every platform can carry a set of device provisioning defaults — device_config — that flow into the config every phone fetches. These defaults resolve through the inheritance chain (platform → account → device), so a value set here applies to every account and device under the platform unless a more specific level overrides it. Network defaults (NTP server, VLAN, QoS), audio, display, regional, and feature settings all live here.

The Device overrides card on a platform's detail page is where super-admins edit that document. It sits directly above the Zero Touch Provisioning card. The card is collapsed by default — expand it to view or edit the JSON. A brand-new platform has no overrides, so the document is an empty {}; that is expected, and devices simply inherit the standard defaults until something is set here.

Editing

1. Open the platform's detail page in the admin portal.
2. Expand the Device overrides card and edit the raw JSON document in the editor.
3. Click Review changes.
4. A dialog summarizes the change as Adds, Changes, and Removes, path by path. Confirm to save, or cancel to keep editing.

Saving replaces the platform's device_config document wholesale.

Guardrails

• Unknown keys are rejected. A typo (for example syslog_sever instead of syslog_server) is refused on save rather than silently dropped, so a misnamed key never appears to "take" without effect.
• Values are range-checked. Network settings are validated server-side (for example VLAN 0–4094, DSCP 0–63, a well-formed NTP/host value). An out-of-range value is rejected with a message naming the field.
• Only device_config is touched. This editor writes nothing else on the platform record.

Notes

• This is a raw JSON editor. A typed, form-based editor with autocomplete is planned as a follow-up.
• The document shape mirrors the provisioning device-settings model: a top-level abstractions object (with audio, display, regional, network, features, provisioning), plus optional vendor_overrides.