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 Edit Incident screen allows updating an existing security incident record and is accessible at /it/security/incidents/:id/edit.

​
Overview

The Edit Incident page loads the existing incident via useSecurityIncident. The form fields include: incident type (data_breach, malware, unauthorized_access, phishing, denial_of_service, policy_violation, other), severity (medium default), discovery date, response status (open, in_progress, resolved, closed), title, description, optional resolved date, and optional resolution notes. On save, updateIncident is called and the user navigates back. The form displays a loading skeleton while the incident data is fetching.

​
Who it’s for

Requires IT_PERMISSIONS.VIEW (outer ITViewGuard). No additional per-route permission gate.

​
Before you start

  • You must hold IT_PERMISSIONS.VIEW to access this screen.
  • The incident must exist in the system.

​
Steps

1

Open the edit form

From the incident detail or list page, navigate to /it/security/incidents/:id/edit.
2

Update incident details

Modify incident type, severity, discovery date, response status, title, description, and any resolution information.
3

Record resolution

If the incident is resolved, set the response status to resolved or closed, enter the resolved date and resolution notes.
4

Save changes

Submit the form to save updates. The page navigates back to the previous screen on success.

​
Key concepts

  • incident_type — Values: data_breach, malware, unauthorized_access, phishing, denial_of_service, policy_violation, other.
  • response_status — Values: open, in_progress, resolved, closed.
  • severity — SecuritySeverity type from src/cores/it/types/security.ts; default medium.
  • resolution_notes — Free-text field to document how the incident was resolved.

IT Service Management

IT Service Management overview.

Governance & parity

Documentation coverage and governance.
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/incidents/EditIncidentPage.tsx