Criticality

Criticality describes the operational importance of an object (low, medium, high), is inherited along the object hierarchy and drives prioritization in rollouts, UI and incidents.

Criticality

Criticality describes the operational importance of an object: low | medium | high. It drives prioritization (e.g. rollouts) and supports SLA/ops decisions — independently of the current Condition state.

Inheritance

Criticality is inherited along the object hierarchy:

Organization → Workspace → Managed Object

If the value is missing on a child object, the parent's value applies. This allows org-wide policies without maintaining every object individually.

Workspaces can set criticality explicitly in the create/edit form.

Effect

Area Effect
Block Rollout Dispatch prioritizes high before medium before low
UI Badges / display in titles and lists
Incident / ISMS Incidents use the same field (high ≈ "critical")

Criticality does not replace conditions: a high object can be OK; a low object can be CRITICAL.

In practice

  1. Set production workspaces to high if rollouts and incidents should be prioritized
  2. Staging/dev to low or medium
  3. Override specific Managed Objects only when needed

Related topics