Skip to main content

Notification settings

Last updated on

Notification settings allow you to control which notification channels are available across your Harness account. These settings are managed at the account scope and apply to all organizations and projects within the account.

By default, all supported notification channels are enabled. Organizations and projects inherit the account-level notification settings and cannot override them.

When a notification channel is disabled at the account level:

  • No notifications are sent through that channel.
  • This applies to both existing and newly configured notifications.
  • Notifications resume automatically when the channel is enabled.

Harness supports the following notification channels:

  • Slack
  • Microsoft Teams
  • Webhooks
  • PagerDuty
  • Email
  • Datadog

Manage notification​

To enable or disable a notification channel, navigate to Account Settings > Account Resources > Default Settings > Notifications, and use the corresponding toggle.

Email filters​

Email filters allow you to restrict where notifications are sent by enforcing a domain allowlist at the account level. When enabled, notifications are delivered only to email addresses included in the allowlist.

Only fixed domains are supported. Expression-based URLs or dynamic domains are not allowed.

Example: If you add example.com to the email filters, only email addresses from that domain such as alerts@example.com will receive notifications.

Emails for platform limit alerts​

Feature Availability

Currently, the platform limit alerts feature is behind the feature flag PL_ENABLE_LIMIT_ALERTS_NOTIFICATIONS. Please, contact Harness Support to enable this feature.

You can configure email recipients to receive alerts as your account approaches the default platform resource limits. Email alerts are sent when usage reaches 80%, 95%, and 100% of the allowed limit, giving you visibility and time to act. You can add up to five email addresses to receive these alerts.

Platform limits are enforced at the account level, and these alerts help you proactively manage usage before limits are reached.

Platform Resource Mapping​

These variables are used in email notifications to alert users when platform resources are approaching their limits. You can find more about the platform resource limits here.

Resource NameResource Variable
OrganizationsMULTIPLE_ORGANIZATIONS
ProjectsMULTIPLE_PROJECTS
SecretsMULTIPLE_SECRETS
User GroupsMULTIPLE_USER_GROUPS
UsersMULTIPLE_USERS
Service AccountsMULTIPLE_SERVICE_ACCOUNTS
VariablesMULTIPLE_VARIABLES
API KeysMULTIPLE_API_KEYS
API Key TokensMULTIPLE_API_TOKENS
ConnectorsMULTIPLE_CONNECTORS
Secret ManagersSECRET_MANAGERS
RolesCUSTOM_ROLES
Resource GroupsCUSTOM_RESOURCE_GROUPS
Role BindingsROLE_ASSIGNMENT
Audit streamingAUDIT_STREAMING_DESTINATION
DelegatesMULTIPLE_DELEGATES
Data SinksDATA_SINKS

Get started with pipeline notifications​

Learn how to notify users of different pipeline events using popular notification methods.

Prerequisites​

Configure New Channels to sent notification​

A new channel can be configured across all scopes. To set up a channel, go to Settings for your desired scope → General → Notification Management, and click Channels as shown below:

  1. Click New Channel and enter a Channel Name.

  2. Choose a Connectivity Mode — you can send notifications either directly through the Harness Platform or via a Harness Delegate.

    connectivity-mode

    If you choose to send notifications through a Harness Delegate, select the appropriate delegate in the Delegate Setup window.

    delegate-mode

  3. Notification Method: Once the connectivity mode is configured, select the Channel Type and add details related to the channel type to proceed.

    note

    If you select the Connectivity Mode as "Connect through a Harness Delegate" and Channel Type as "Email", ensure to add an SMTP configuration to which the Harness delegate has access. If this is not done, then the Email notifications will fail.

Configure pipeline notifications​

  1. Select the Notify icon on the right side of the Harness pipeline studio.
  2. In New Notification, add a name for your notification.
  3. In Pipeline Events, select the events (pipeline or stages) that will trigger the notification.
    • For stage-based events, select the stage name that you want to trigger the notification and click Next.
  4. In Notification Method, select Email. For email notifications, simply type in the email addresses that you want to notify.
    • Enter multiple addresses as a comma-separated list. For example, john.doe@example.io,qateam@example.io.
    • Additionally, use the user group that you created above to receive notifications.
    • You can also use the user group that you created above to receive notifications.
  5. You can optionally add notification templates to get custom notifications based on the event. To learn more, go to Custom Notification templates for Pipeline Notifications.
  6. Select the Connectivity Mode.
    • Connect through Harness Platform to send notifications.
    • Connect through Harness Delegate to send notifications.
      • Select the delegate that you want to use to send notifications.
  7. Select Submit and your notification is created.

More detailed information on how to configure the notification at the receiver end can be found here.

When you run the pipeline, you'll receive notifications on the platform you set up.