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 Requirement screen allows updating an existing compliance requirement and is accessible at /it/security/compliance/requirements/:id/edit.

​
Overview

The Edit Requirement page loads the existing compliance requirement via useComplianceRequirement. The form fields include: requirement name, compliance framework (hipaa_it, soc2, iso27001, other), requirement description, requirement category (access_control, data_protection, incident_response, other), compliance status (not_assessed, compliant, non_compliant, in_progress), next assessment date, and assessment notes. On save, updateRequirement is called. A loading skeleton is shown while data loads, and a back-navigation button is provided.

​
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 compliance requirement must exist.

​
Steps

1

Open the edit form

Navigate to /it/security/compliance/requirements/:id/edit from the compliance requirements list.
2

Update requirement details

Modify the name, framework, description, category, compliance status, next assessment date, and notes.
3

Save changes

Submit the form to save updates and navigate back.

​
Key concepts

  • compliance_framework — Values: hipaa_it, soc2, iso27001, other.
  • requirement_category — Values: access_control, data_protection, incident_response, other.
  • compliance_status — Values: not_assessed, compliant, non_compliant, in_progress.
  • next_assessment_date — Date string stored as ISO format; displayed as date-only input (split at T).

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/compliance/EditComplianceRequirementPage.tsx