Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

The SLA Instances page lists every SLA instance tracked by your organization, grouped by status, and allows authorized users to take management actions on individual instances. It is reached at /settings/sla/instances.

Overview

SLA Instances represent runtime tracking of SLA compliance against specific records. The page loads all instances for the current organization and lets you filter by status. Instance rows display the SLA definition name, the entity being tracked, start date, and deadline. Clicking a row (when you have pf.sla.instance.manage) opens an action dialog. Status values visible in the UI: Active, At Risk, Paused, Breached, Completed.

Who it’s for

Requires pf.sla.view (route guard). Action buttons additionally check pf.sla.instance.manage at the component level.

Before you start

  • SLA definitions must exist. Create them at Settings → SLA → Definitions (/settings/sla/definitions).
  • Instances are created automatically when an SLA-monitored event occurs; they are not manually created on this page.

Steps

  1. Navigate to Settings → SLA → SLA Instances (/settings/sla/instances).
  2. Use the Filter status dropdown to narrow the list (All / Active / At Risk / Paused / Breached / Completed).
  3. Review the count shown in the card header.
  4. Click a row to open the action dialog (requires pf.sla.instance.manage).

Key concepts

SLA Instance — a runtime record that tracks compliance of a specific entity against an SLA definition, with a started_at and deadline_at. Status lifecycle — instances move through active → at_risk → breached or active → completed; paused suspends the clock.

Platform Foundation

Platform Foundation overview.

Governance & parity

This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/platform.tsx
  • src/platform/sla/pages/SLAInstancesPage.tsx
  • src/platform/sla/hooks/useSLAInstances.ts
  • src/platform/sla/components/SLAInstanceActionDialog.tsx