Notification defaults

Overview

Notification defaults let you set an account-wide default recipient email address and default email template for notifications. Every new alert or monitoring configuration you create across Turbo360 starts from these defaults, so your team never has to re-enter the same values each time they set up monitoring.

Notification defaults are managed from the Email templates page and are available on SaaS accounts only.

Business value

Notification defaults eliminate the need to manually set a recipient and template on every new alert configuration across modules.

Prerequisites

You must be signed in as the Account owner to manage notification defaults.

Required permissions

Only the Account owner can view and edit notification defaults.

How it works

Notification defaults consist of two values:

• Recipient email: the default email address pre-filled as the notification recipient in every new alert configuration.
• Email template: the default email template applied to every new alert configuration.

These defaults are displayed as a strip at the top of the Email templates page, showing the current recipient address and template name alongside an Edit control.

When you create a new alert or monitoring configuration in Business Applications, Cost Analyzer, Business Activity Monitoring, or Azure Documenter, the recipient and template fields are pre-filled with the current defaults. You can still override them per configuration if needed.

Default behaviour

A few rules govern how defaults are applied:

• Always inherited, no action required. New configurations pick up the current defaults automatically. You do not need to opt in each time.
• Empty recipient means no alerts. Configurations with no recipient set are never silently switched on by the defaults. Opt-out is always respected.
• Defaults are a starting point, not a lock. Any individual configuration can override the default recipient or template without affecting others.
• No account default set. If no default recipient has been configured, notifications fall back to the signed-in user's own email, as before.

Channel-specific behaviour

Notification defaults apply to email-based notification channels. Two channels have fixed behaviour that is not affected by the configured defaults:

• Azure DevOps: always uses the system template, regardless of the default email template configured. You cannot override the template for this channel.
• SMTP: requires an email template explicitly configured for the SMTP channel. The account-wide default email template is not applied to SMTP notifications.

Updating existing configurations

When you save new defaults, you can choose whether to apply them to configurations that already exist. Three options are available:

• Don't update (default): only new configurations use the updated defaults. Existing configurations are not changed.
• Update ones still using the old default: applies the new defaults to configurations that were never individually customized. Configurations with custom recipient values are left untouched.
• Update all configurations: overwrites every configuration across the selected modules, including those with custom recipient addresses or templates. This option is marked as Destructive and should be used with care.

When you select Update ones still using the old default or Update all configurations, a module selector appears so you can scope the update to specific modules: Business Applications, Cost Analyzer, Business Activity Monitoring, and Azure Documenter.

Steps

Set notification defaults

Setting defaults pre-fills the recipient and template fields for all future alert configurations.

1. Navigate to Settings > Email templates.
2. In the Notification defaults strip at the top of the page, click Edit.
3. Enter the Recipient email address to use as the default.
4. Select the Email template to use as the default.
5. Click Save.

Apply defaults to existing configurations

Use this when you want to push updated defaults to configurations that already exist.

1. Navigate to Settings > Email templates.
2. Click Edit in the Notification defaults strip.
3. Set the Recipient email and Email template values.
4. Under Update existing configurations, expand the section and select one of the following options:
   • Don't update: existing configurations are unchanged.
   • Update ones still using the old default: updates configurations that have never been individually customized. Select which modules to include.
   • Update all configurations: overwrites all configurations, including those with custom values. Select which modules to include.
5. Click Save.

Configuration

Permission behavior

With access (Account owner):
You can view and edit notification defaults, including applying changes to existing configurations.

Without access (all other roles):
The Email templates page is inaccessible. Notification defaults cannot be viewed or edited.

Limitations

• Notification defaults are only available on SaaS accounts.
• Only the Account owner can set or change notification defaults.
• Configurations with no recipient set are not affected by any update option.
• The Azure DevOps notification channel always uses the system template. The configured default email template does not apply.
• The SMTP notification channel requires an email template configured specifically for SMTP. The account-wide default email template is not applied.

Troubleshooting

1. The Edit control in the Notification defaults strip is not clickable.
   Cause: Only the Account owner can edit notification defaults.
   Fix: Confirm you are signed in as the Account owner. If you are not the Account owner, contact your administrator.

2. New configurations are not picking up the updated defaults.
   Cause: The defaults may not have been saved after editing.
   Fix: Return to Settings > Email templates, click Edit in the Notification defaults strip, and confirm the values are correct. Click Save to apply.

3. Existing configurations still show the old recipient after applying defaults.
   Cause: The update option selected was Don't update, or the configurations had custom values and Update ones still using the old default was used.
   Fix: To update configurations with custom values, use Update all configurations and select the relevant modules. Note that this is a destructive action.

4. The module selector is not appearing.
   Cause: The module selector only appears when Update ones still using the old default or Update all configurations is selected.
   Fix: Expand the Update existing configurations section and select one of those options to reveal the module selector.

5. Notification defaults strip is not visible on the Email templates page.
   Cause: Notification defaults are only available on SaaS accounts.
   Fix: Confirm your account type. If you are on a private-hosted deployment, this feature is not available.

Related articles

• Email templates
• Managing notification channels
• Escalation policies