User Guide

How to configure notification defaults for new Sites

This guide shows you how to edit the instance-level notification template defaults that AlloyScan copies into every newly created Site.

These defaults are different from the per-Site notification templates. The defaults live at the App-management level and are applied only at the moment a new Site is created. Edits made here do not propagate to Sites that already exist.

Prerequisites

Note: This page covers instance-level administration in App Management. It is used by Global Administrators.

  • You are signed in as a Global Administrator. App-management screens are not visible to Site Administrators.
  • You know which categories and templates need to change for the next batch of Sites you intend to create.

Steps

  1. Navigate to Admin Center > App management > Site template > Notification templates.
  2. Expand the four category cards — System, Administrative, Standard, Conditional. The layout is the same as the per-Site Notification templates screen.
  3. Edit the templates you need to seed differently (subject, body, recipients).
  4. Save.

Verify

These defaults are copied at Site creation. To verify the seed actually applies:

  1. Create a new Site (Admin Center > App management > Sites > + New site).
  2. Open the new Site's Admin Center > Site Settings > Notifications > Notification templates.
  3. The templates you edited in the App-management defaults appear in the new Site with the new content.

Existing Sites you created before this edit are unaffected and continue to carry whatever was seeded at their creation time, unless an administrator has since edited them per-Site.

When to edit defaults vs per-Site

Goal Edit here?
Change templates for all future Sites you create Yes — edit the App-management defaults.
Change templates for one existing Site No — edit per-Site instead.
Change templates for all existing Sites at once Not supported through templates alone. You need to edit each existing Site's templates by hand.

Limitations

  • The set of fields exposed on each template (subject, body, recipients, conditions) may vary by deployment.
  • Some templates carry an indicator suggesting they are "customizable per-site"; once a Site overrides such a template after creation, subsequent edits to the App-management default do not back-propagate.