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.

Security alert configuration page at /settings/security-alerts where administrators define which security events generate alerts, set their severity, and enable or disable individual rules.

​
Overview

The Security Alert Configuration page provides a CRUD interface for the pf_security_alert_configs table. Each config record specifies an alert_name, an event_type (one of: failed_login, permission_violation, suspicious_activity, account_lockout, mfa_failure), a severity (one of: info, warning, error, critical), and an is_active toggle. Admins can create, edit, and delete configurations via dialogs. Delete requires confirmation. The page is gated by pf.security_alerts.manage.

​
Who it’s for

Required permission: pf.security_alerts.manage

​
Before you start

  • You must hold the pf.security_alerts.manage permission.
  • Determine which event types and severity thresholds are relevant to your organization’s security posture.

​
Steps

  1. Navigate to /settings/security-alerts.
  2. Review existing alert configurations in the table.
  3. To add a new alert rule, click New Alert and complete the form.
  4. To edit an existing rule, click its edit icon.
  5. To enable or disable a rule, toggle the Active switch on the rule.
  6. To remove a rule, click its delete icon and confirm.

​
Key concepts

event_type — The security event category that triggers this alert. Available types: failed_login, permission_violation, suspicious_activity, account_lockout, mfa_failure. severity — The urgency level assigned to the alert: info, warning, error, or critical. is_active — Whether the alert rule is currently evaluating incoming events.

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/security/pages/SecurityAlertConfigPage.tsx
  • src/platform/security/hooks/useSecurityAlertConfigList.ts