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.

Administrators can manage notification templates at /settings/notifications/templates. This route renders NotificationTemplatesPage and is accessible to users with the pf.notification_templates.manage permission (checked at the component level via PF_PERMISSIONS.NOTIFICATION_TEMPLATES_MANAGE).

​
Overview

The Notification Templates page displays all notification templates grouped and sorted by event_key then channel. A collapsible filter panel allows filtering by event key and channel. A search field filters by template name, event key, or channel. Administrators with pf.notification_templates.manage can create new templates and edit existing ones via TemplateEditorSheet. The TemplateStatusToggle component controls whether each template is active. Templates are fetched via useNotificationTemplates().

​
Who it’s for

Requires permission: pf.notification_templates.manage (checked at component level).

​
Before you start

  • Your account must have the pf.notification_templates.manage permission.

​
Steps

  1. Navigate to Settings > Notifications > Templates (/settings/notifications/templates).
  2. Use the search field or filters to find the template you want to modify.
  3. Select the edit icon on a template row to open the TemplateEditorSheet.
  4. Update the template content and save.
  5. Use the status toggle to activate or deactivate a template.

​
Key concepts

Event key — A string identifier for the notification trigger event (e.g., form_submitted, task_assigned). Each event key can have templates for multiple channels. Channel — The delivery mechanism: email, sms, in_app, or push. One template per event-channel combination.

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/notifications/pages/NotificationTemplatesPage.tsx
  • src/platform/notifications/hooks/useNotificationTemplates.ts