Preset Creation Flow
Notification Center supports both system-generated and user-created presets. Each flow defines how message templates are created, extended, and customized for notification delivery. The sections below show how presets are built and modified in Notification Center.
Understand preset creation paths
There are two preset creation paths: basic and advanced.
| Flow type | Description |
|---|---|
| Basic flow | Uses a system-provided preset with default message templates. |
| Advanced flow | Creates a new custom preset that can modify or extend existing templates. |
View preset creation flow
Flow summary: How users create and customize presets
- Basic flow: Use the built-in system preset without editing. The message follows the predefined template for the selected destination type.
- Advanced flow: Create a custom preset to edit message content or add override templates.
- Define a general message template as the base for all notifications using this preset.
- Add override templates for specific entity subtypes such as metric threshold or logs immediate alerts.
- Notification Center merges the general and override layers when rendering messages.
Basic flow: use a system preset
System presets are available by default for each destination type. They use preconfigured message templates aligned with the entity type and destination type schema. System presets work for most use cases. Use a system preset when you do not need to customize notification messages.
Advanced flow: create a custom preset
Use a custom preset when you need to modify or extend message content.
- Select Integrations, then Notification Center, then Presets.
- Open the tab for the entity type you want to configure (Alert or Case).
- Select the destination type for the new preset.
- Select Create new preset.
- Modify the general message template or add override templates for specific subtypes.
- Save the preset.
The new preset becomes available and can be reused across multiple connectors.
Note
Aim for one variation per preset to keep routing simple and reduce template maintenance.
Next steps
- Dynamic templating: Use Tera expressions to enrich and personalize preset content
- Message rendering: Understand how general and override templates merge at runtime
- Routing overview: Attach new presets to destinations through routing rules
