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.

This page displays the detail view for a single security patch record, including its deployment status across IT assets. Navigate to it at /it/security/patches/:id.

​
Overview

The Patch Details page shows patch metadata (Patch ID, Name, Severity badge, Status badge, Release Date, Vendor, Affected Software, Description) and a deployment table listing each asset row with its deployment status, deployed date, and notes. A progress bar summarizes deployed vs. total asset count. The Edit button navigates to /it/security/patches/:id/edit.

​
Who it’s for

This route is protected by IT_PERMISSIONS.VIEW (it.view) via the module-level ITViewGuard. No additional per-route permission gate exists beyond the module guard.

​
Before you start

  • The patch record must already exist. Use the New Patch page to create one.

​
Steps

  1. Navigate to IT > Security > Patch Tracking and click a patch’s ID or name, or navigate directly to /it/security/patches/:id.
  2. Review the patch metadata in the header and summary cards.
  3. Review the Deployment Status table to see which assets have received this patch.
  4. Click an asset name in the table to navigate to that asset’s detail page.
  5. Click Edit (top right) to modify patch metadata.

​
Key concepts

  • Patch ID — the vendor-assigned identifier (e.g., KB5034441), displayed in monospace.
  • Deployment status — per-asset statuses include deployed, failed, not_applicable, and a default pending state.
  • DeploymentProgressBar — visual indicator of deployed / total asset count.
  • SeverityBadge — visual severity indicator (critical, high, medium, low).

IT Service Management

IT Service Management 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/it.tsx
  • src/cores/it/pages/security/patches/PatchDetailPage.tsx
  • src/cores/it/hooks/useSecurityPatches.ts
  • src/cores/it/hooks/usePatchDeployments.ts
  • src/cores/it/types/security.ts