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, short label, environment label and time zone. The environment label (for example Production or Staging) is shown as a tag beside the facility name in the top bar; the short label is saved with the profile but not shown elsewhere. Time zone underpins every other section's time-of-day logic (operating hours, freshness windows, incident timestamps). | Facility Admin |
| Operating hours | Two questions: which days your suites are busy (Weekdays, Every day, or Custom per day) and what hours. Drives maintenance-collision detection — a scrub forecast to still be running when hours begin is flagged — and playback incident severity. | Facility Admin |
| Playback & workloads | What each suite plays: format (codec at a resolution, from the built-in library or a custom format), frame rate and streams at the same time. Pillar works out the read rate each suite needs for playback risk and incident impact. | Facility Admin |
| Capacity & risk | When a pool counts as getting full (warning, critical, planning lead time), drive temperature limits, and playback targets. Forecasting, latency detection, data freshness, SMART, network, saturation and playback tuning sit under Advanced. | Facility Admin |
| Context mapping | Human-readable labels and metadata (client, project, suite) attached to storage systems, pools, or datasets by system 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 | The install command for a new storage system (with a single-use pairing code), plus the roster of paired systems with rotate/revoke API-key actions. | Facility Admin |
2.Saving Changes
The list of sections shows each one's current value in a single line, and every setting says what it changes in plain words beside the control. Each section has one save bar at the bottom that always says whether anything is pending, with Discard changes and Save changes. If someone else saved the same settings after you opened the page, your save is refused and you are offered the latest version instead of overwriting theirs. Leaving with unsaved changes asks first. Alert routing, connected apps, member roles and pairing apply as soon as you change them.
3.Playback & Workloads: the Format Library
A workload profile is a format, a frame rate, how many streams play at once, and the suite it applies to. The built-in library covers Apple ProRes (Proxy to 4444 XQ), Avid DNxHR and DNxHD, Sony XAVC, ARRIRAW, REDCODE, Blackmagic RAW, DPX, OpenEXR and H.264/HEVC proxies, and the resolution is chosen separately, from presets or any custom size. Rates come from the vendors' published figures (Apple's ProRes White Paper, Avid's DNx data-rate tables, Blackmagic and RED specifications) or, for uncompressed formats, from the frame size; each profile says whether its figure is published, scaled from a published size, derived, or approximate.
For anything else, choose Custom format in the Codec list and enter a name, the frame size and the data rate of one stream from your encoder or camera spec sheet. Custom formats are saved with the profiles that use them and can be picked again from any other profile.
4.Read-Only Access
People with access to Settings can view configuration including thresholds, routing, and the paired-system 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 system API keys are an exception: copy them securely when shown.
5.Agent pairing
The Agent pairing section gives you one install command for a new storage system. It downloads the signed installer, installs the Pillar agent and links the system to your organization; the command carries a single-use pairing code that expires 15 minutes after it is created. It works on Unraid, TrueNAS SCALE, Ubuntu/Debian and Synology DSM. The section also lists every paired system with its status (Reporting, Degraded, Offline or Uninstalled) and two per-system actions: rotate the system's API key (issues a new key and invalidates the old one) or revoke it (the system 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