# 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

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).\
For supported destinations, see [Destination types](https://coralogix.com/docs/user-guides/notification-center/destination-types/introduction/index.md).

## 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.

## Create a custom preset

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

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

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

1. Select the destination type for the new preset.

1. Select **+ New preset**.

1. Enter a name and description.

1. 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.

1. 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.

1. Select **Create preset** to save.

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

## Edit an existing preset

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

Changes apply automatically to all router destinations using that preset.

## 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

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://coralogix.com/docs/user-guides/notification-center/presets/message-render-flow/index.md)
- [Preset creation flows](https://coralogix.com/docs/user-guides/notification-center/presets/preset-creation/index.md)

## Check required permissions

Creating or editing presets requires specific permissions.\
See [Roles and Permissions](https://coralogix.com/docs/user-guides/aaa/access-control/policies/index.md).

## 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**.
1. Open the **Cases** entity type tab.
1. Select the destination type, then **Create new preset**.
1. Edit the message template using `_context` variables for dynamic Case metadata.
1. Save the preset.

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

## Next steps

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