Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fuser-guides%2Fnotification-center%2Fpresets%2Fintroduction.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fuser-guides%2Fnotification-center%2Fpresets%2Fintroduction.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[API reference](https://docs-docusaurus.kinsta.page/api-reference/v5/presets-service/.md)[Terraform](https://registry.terraform.io/providers/coralogix/coralogix/latest/docs/resources/preset)

# Presets overview

A preset defines the message content and format for notifications sent from Coralogix to external systems such as Slack, PagerDuty, or Generic HTTPS. Each preset determines what data is included in a notification and how it is formatted. Presets can be reused across multiple connectors to maintain consistent message structures.

## Understand preset types[​](#understand-preset-types "Direct link to Understand preset types")

Notification Center supports two preset types:

| Preset type       | Description                                                                           |
| ----------------- | ------------------------------------------------------------------------------------- |
| **System preset** | A read-only preset provided by Coralogix. Use this when no customization is required. |
| **Custom preset** | A user-defined preset that allows full customization of message templates and logic.  |

Each preset follows the schema of its destination type and entity (alert or case).<br /><!-- -->For supported destinations, see [Destination types](https://docs-docusaurus.kinsta.page/user-guides/notification-center/destination-types/introduction/.md).

## Understand preset layers[​](#understand-preset-layers "Direct link to Understand preset layers")

Presets are composed of configuration layers that define the final rendered message.

| Layer              | Purpose                                                                          |
| ------------------ | -------------------------------------------------------------------------------- |
| **General layer**  | Defines the default template for all notifications using this preset.            |
| **Override layer** | Defines subtype-specific templates. Overrides the general layer when applicable. |

At runtime, Notification Center merges these layers to produce the final message payload.

[![Preset creation flow in Notification Center](/assets/images/preset-07a6736cabed60dcddbfb67438b69217.webp)](https://docs-docusaurus.kinsta.page/assets/images/preset-07a6736cabed60dcddbfb67438b69217.webp)

## Create a custom preset[​](#create-a-custom-preset "Direct link to Create a custom preset")

Use presets to define message content for a specific destination type:

1. Select **Integrations**, then **Notification Center**, then **Presets**.

2. Open the tab for the entity type you want to configure (Alert or Case).

3. Select the destination type for the new preset.

4. Select **+ New preset**.

5. Enter a name and description.

6. In the **Message** section, configure the template:

   * **General**: Pre-populated from the system preset to help you get started. Modify the fields available for your destination type.
   * **Override templates** (optional): Add subtype-specific overrides.
   * Use the **Preview** panel to view the rendered message.

7. Select **Send test notification** to verify output.

   * Select a connector for delivery.
   * Notification Center sends a test payload using an example schema.

   Note

   Dynamic connector fields are ignored for test notifications.

8. Select **Create preset** to save.

The new preset becomes available for reuse across connectors and routing rules.

## Edit an existing preset[​](#edit-an-existing-preset "Direct link to Edit an existing preset")

1. In the **Presets** tab, locate the preset you want to modify.
2. Select **Edit** from the **Actions** menu.
3. Update variables, templates, or logic.
4. Select **Save changes**.

Changes apply automatically to all router destinations using that preset.

## Manage existing presets[​](#manage-existing-presets "Direct link to Manage existing presets")

Manage all configured presets from the **Presets** list. Each entry shows its name, preset type, and last update date.

Available actions:

* **View** preset configuration
* **Edit** templates and logic
* **Duplicate** a preset to reuse configuration
* **Delete** unused presets
* **Send test notification** to validate output

Presets referenced in routers or connectors must be unlinked before deletion.

## Understand notification rendering[​](#understand-notification-rendering "Direct link to Understand notification rendering")

When an alert or case triggers a notification, Notification Center merges preset layers to build the final message. The rendering flow differs for system presets and custom presets.

See the following for more detail:

* [Preset message rendering flow](https://docs-docusaurus.kinsta.page/user-guides/notification-center/presets/message-render-flow/.md)

* [Preset creation flows](https://docs-docusaurus.kinsta.page/user-guides/notification-center/presets/preset-creation/.md)

## Check required permissions[​](#check-required-permissions "Direct link to Check required permissions")

Creating or editing presets requires specific permissions.<br /><!-- -->See [Roles and Permissions](https://docs-docusaurus.kinsta.page/user-guides/aaa/access-control/policies/.md).

## Case presets[​](#case-presets "Direct link to Case presets")

Presets for Cases follow the same structure as alert presets, but use the `_context` variable to access Case metadata such as state, status, priority, and assignee.

Coralogix creates a default system preset automatically the first time you create a connector for a destination type. The system preset covers most notification needs without customization. Start with the default system preset and create a custom preset only when you need to modify the message format.

To create a Case preset:

1. Select **Notification Center**, then **Presets**.
2. Open the **Cases** entity type tab.
3. Select the destination type, then **Create new preset**.
4. Edit the message template using `_context` variables for dynamic Case metadata.
5. Save the preset.

See [Dynamic templating](https://docs-docusaurus.kinsta.page/user-guides/notification-center/dynamic-templating/.md) for the full list of available Case variables.

## Next steps[​](#next-steps "Direct link to Next steps")

Learn how general and override layers merge at runtime in [Preset message rendering flow](https://docs-docusaurus.kinsta.page/user-guides/notification-center/presets/message-render-flow/.md).