The Compliance Requirements screen lists all IT compliance requirements with filtering and is accessible atDocumentation Index
Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
Use this file to discover all available pages before exploring further.
/it/security/compliance/requirements.
Overview
The Compliance Requirements page loads requirements viauseComplianceRequirements with optional filter parameters. A search box and three filter dropdowns are provided: Framework (hipaa_it, soc2, iso27001, other), Category (access_control, data_protection, incident_response, other), and Status (compliant, non_compliant, in_progress, not_assessed). The data table shows requirement name (clickable, navigates to detail), framework badge, category label, compliance status badge, last assessment date, and next assessment date. An Add Requirement button links to the new-requirement form. The back button navigates to /it/security/compliance.
Who it’s for
RequiresIT_PERMISSIONS.VIEW (outer ITViewGuard). No additional per-route permission gate.
Before you start
- You must hold
IT_PERMISSIONS.VIEWto access this screen.
Steps
Open Compliance Requirements
Navigate to
/it/security/compliance/requirements. All requirements load by default.Filter requirements
Use the search box to filter by requirement name. Use the Framework, Category, and Status dropdowns to narrow results.
Key concepts
- compliance_framework — Values:
hipaa_it(displayed as “HIPAA IT”),soc2(SOC 2),iso27001(ISO 27001),other. - requirement_category — Values:
access_control,data_protection,incident_response,other. - compliance_status — Values:
compliant,non_compliant,in_progress,not_assessed. - last_assessment_date / next_assessment_date — Track when the requirement was last evaluated and when the next review is due.
Related
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.
Documentation sources
Documentation sources
- src/routes/it.tsx
- src/cores/it/pages/security/compliance/ComplianceRequirementListPage.tsx