Find a guide, feature, or API endpoint. Try “FTP”, “alerts”, or “instruments”.

Browse documentation

Docs/Platform guides

Contact groups and email notifications

Prepare recipients and templates, attach email actions, and follow delivery outcomes.

On this page

Anomaly email actions use organization-level Contact Groups and Email Templates. These resources are separate from project data permissions.

Build a contact group

  1. Open the organization management area and select Contact Groups.
  2. Create a group with a recognizable purpose, such as “North site reviewers.”
  3. Add email addresses manually, paste contacts using the import control, or select organization users or team users to import.
  4. Review names and addresses, resolve duplicate entries, and save.

Review the saved contact list after importing users. Adding recipients to a contact group does not grant them dashboard or instrument access. Configure application access separately.

Create an email template

Open Email Templates and create a template with a name, a one-line plain-text subject, and a Markdown body. Use the placeholder picker to insert supported values:

Placeholder Purpose
{{anomaly_name}} The detected definition’s name.
{{timestamp}} The occurrence timestamp.
{{project_name}} Project context.
{{site_names}} Site context.
{{recipient_email}}, {{recipient_name}} Recipient details.
{{severity}} Configured severity.
{{passed_condition}} Condition evidence in the body.

The subject does not support passed_condition. Preview the template and verify its placeholders before using it in a definition.

An example subject is {{severity}}: {{anomaly_name}} — {{project_name}}. In the body, identify the project and timestamp, include condition evidence, and explain your team’s review process.

Attach the notification

Edit an anomaly definition, add Email Notification, choose contact groups and a template, and configure Trigger Cooldown in minutes. SanSignal sends a separate provider message to each deduplicated recipient.

An unavailable or archived notification resource can cause an action to be skipped. Inspect warnings on the action and review affected definitions before retiring a group or template.

Permissions and delivery

Organization administrators can assign notification viewer or manager access without making someone an organization administrator. Configuring an email action requires access to inspect its contact groups and templates.

Review Action executions on a detected anomaly to see progress and outcomes. Provider acceptance means the email service accepted the message; it is not a guarantee of inbox delivery. If a message is missing, check the recorded action result, recipient address, and the recipient’s mail filtering.