Settings
Settings is organized into eight sections, each independently permissioned and independently saved. This page maps each section to what it configures and who can edit it.
1.The Eight Sections
| Section | Configures | Edit requires |
|---|---|---|
| Facility | Facility name and timezone. Timezone underpins every other section's time-of-day logic (operating hours, freshness windows, incident timestamps). | Facility Admin |
| Operating Hours | Per-day open/closed windows (up to a fixed number of windows per day). Drives maintenance-collision detection — a scrub forecast to still be running when hours begin is flagged. | Facility Admin |
| Playback & Workloads | Codec/frame-rate profiles and their required throughput, applied to nodes, pools, or datasets. Feeds the frame-budget math shown on Metrics & evidence. | Facility Admin |
| Capacity & Risk | Capacity warning/hard thresholds, rapid-growth and rapid-ingest detection, temperature thresholds, latency outlier/tail thresholds, and telemetry freshness windows (live/delayed/stale). | Facility Admin |
| Context Mapping | Human-readable labels and metadata (client, project, suite) attached to nodes, pools, or datasets by node key, pool id, or dataset path/CIDR match. | Facility Admin |
| Alerts & Integrations | Which event classes route to which destinations (Slack, Discord, PagerDuty, Opsgenie, email, webhook), plus connecting/testing/disabling each destination. | Facility Admin |
| Users & Roles | Per-member Pillar role overrides on top of their Clerk organization role. Inviting new members is delegated entirely to Clerk's own organization UI. | Organization Admin (narrower than the other sections) |
| Agent Pairing | Claim-token generation and install command for new nodes, plus the roster of already-paired nodes with rotate/revoke API-key actions. | Facility Admin |
2.Read-Only Access
People with access to Settings can view configuration including thresholds, routing, and the node roster. Treat these values and labels as potentially sensitive operational metadata. Roles without the required edit permission see the exact same values with every control disabled rather than a separate, stripped-down view. Saved integration secret fields are masked in read responses. Newly generated node credentials are an exception: copy them securely when shown.
3.Agent Pairing Roster
Beyond generating new claim tokens, the Agent Pairing section lists every already-paired node for the facility with status (online/degraded/offline) and two per-node actions: rotate the node's API key (issues a new key and invalidates the old one) or revoke it (the node can no longer authenticate at all until re-paired). Both actions require confirmation and are logged. Rotation invalidates the old key immediately; securely update the host configuration with the newly issued key and verify a fresh heartbeat. Revocation stops authentication but does not uninstall the Agent or delete cloud history.
See also