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, report definitions, Change tracking configuration, the Tools catalog, and Snapshot storage settings. After creation, the new Site lives a fully independent life and is no longer linked to the template.

This page covers what the Site Template is, why it exists, and the single load-bearing 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-global, visible only to Global Administrators.

Six subsystems are seeded:

• Notification templates
• Reports
• Web reports
• Change history tracking
• Tools
• Snapshot storage

Each subsystem is a separate page in App Management with the same shape as its per-Site counterpart in Site Settings.

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 a snapshot of every Site Template subsystem into the new Site as that Site's per-Site configuration.
3. From that point on, the new Site's per-Site Notifications, Reports, Web reports, Change tracking, Tools, and Snapshot storage records are decoupled from 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, a report, or a Tools entry on the App Management Site Template page does not modify any Site that already exists. Existing Sites continue to carry whatever was seeded into them when they were created.

This is the single most common source of confusion when administrators expect the Site Template to behave like instance-wide policy. It does not. It is bootstrap configuration only.

To change configuration for an existing Site, edit it per-Site through the corresponding Site Settings page.

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 baseline policy. The Site Template is a useful place to record what "good defaults" look like for your organization, even if existing Sites have drifted away from it.

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 seeds, not enforcement.

Related

• How to configure the Site Template
• Site Template Reference
• About App Management
• About Sites