Administration Guide

About Site template

The Site template is the instance-wide bundle of default configuration that AlloyScan copies into every newly created Site at the moment of creation. It seeds Notification templates, Analytics charts, Change tracking configuration, and the Tools catalog. After creation, the new Site is no longer linked to the template.

This page covers what the Site template is, why it exists, and the key fact about how it propagates: it does not update existing Sites.

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

Where the Site template lives

  • Admin Center > App management > Site template — instance-level and visible only to Global Administrators.

Four areas are available under Site template:

  • Notification templates
  • Analytics
  • Change tracking
  • Tools

Each area is a separate page in App management with the same purpose as its counterpart in Site administration.

How seeding works

When a Global Administrator creates a new Site (Admin Center > App management > Sites > + New Site), AlloyScan:

  1. Creates the Site shell with the chosen Title, Slug, and Time zone.
  2. Copies the current Site template defaults into the new Site as that Site's configuration.
  3. From that point on, the new Site's Notification templates, Analytics, Change tracking, and Tools records are independent of the template.

A Site Administrator on the new Site sees the seeded records as if they had been configured directly on the Site.

The load-bearing fact

Important: Site template edits are not retroactive. Changing a Notification template, an Analytics chart, or a Tools entry under App management > Site template does not modify any Site that already exists. Existing Sites continue to use the defaults copied when they were created.

The Site template provides initial configuration; it does not act as an instance-wide policy for existing Sites.

To change configuration for an existing Site, switch to that Site and use the corresponding Admin Center page.

Site template area Per-Site equivalent
Notification templates Admin Center > Notifications > Notification templates
Analytics Analytics
Change tracking Admin Center > Settings > Change tracking
Tools Admin Center > Settings > Tools

When to edit the Site template

  • Onboarding waves. When you are about to create many new Sites with similar configuration, edit the Site template first, then create the Sites.
  • Establishing defaults. Use the Site template to define the initial configuration for future Sites.

When not to rely on the Site template

  • To change every existing Site at once. This is unsupported through templates. You need to walk each existing Site by hand or build automation that calls the per-Site edit surfaces.
  • As live policy. Site template records are defaults, not enforcement.