Protect Critical Incident Metadata with Read-only Fields

Protect critical incident metadata from human error. You can now add read‑only fields to your incident forms so commanders see important context (e.g., where the incident was created: Slack vs Web) but cannot change it. Locking down these values preserves data integrity, prevents fat‑finger edits that break automation, and ensures your analytics and post‑incident reviews are based on consistent, trustworthy data.

What You Get

• Immutable fields on forms: Read‑only fields render on your create/update forms for visibility, but can’t be edited by users (including incident commanders).
• Stronger automation guarantees: Downstream workflows that depend on specific field values won’t be skipped or misfired due to manual overrides.
• Better reporting quality: Eliminate drift in key incident attributes so your dashboards, SLO/SLA reports, and retros stay accurate.

How It Works

1. Go to the form field that you want to define as read-only in Configuration → Forms.
2. Enable Read‑only: Toggle Read‑only for that field.
   
   1. When enabled, the field’s value on forms is locked to its default value and cannot be overwritten by users.
   2. You must set a default value before you can enable Read‑only.

Add to your forms: Include the field on the incident forms you present to commanders. The value will display for context but won’t be editable.

Note: Because the value is locked, use read‑only on metadata you want to standardize and protect from manual edits.