Configuration

The SG-Admin Configuration pillar — site-wide configuration beyond Appearance.

The Configuration pillar in the admin is the per-site surface for site-wide configuration that doesn't fit into Appearance — site identity, integrations setup, operational toggles. Where Appearance handles visual configuration, Configuration handles operational and identity configuration. This page is the Reference definition.

What is this for?

Read this page when you want the structural definition of site-wide non-visual configuration.

Good use cases

• You are scoping site identity / SEO / integration configuration.
• You hit a "where do I set the site name?" question.

What NOT to use this for

• Per-step procedures — open the relevant Guide.
• Visual configuration — open Appearance.

How this connects to other features

• SG-Admin Overview — parent.
• Tools — sibling.
• Migration — sibling.
• Appearance — visual configuration counterpart.

Where to find it

Open SG-Admin for the active site. Configuration is in the sidebar under the settings group. Site identity, integrations, SMTP, and operational toggles are grouped as sub-surfaces. Admin access is required.

Definition

The Configuration pillar groups site-wide non-visual configuration surfaces — site identity (name, tagline, default OG image), integrations setup (per-site integration configuration), email transport (SMTP), audit / activity preferences, and operator-facing toggles for site-level behavior.

Purpose

Define the Configuration pillar as a Reference layer.

Scope

Covers the surfaces inside Configuration. Does not cover visual configuration (Appearance) or per-step procedures.

Surfaces inside Configuration

Site identity

Site name, tagline, default OG image, contact information.

Integrations

Per-site integration configuration entry — pairs with the Integrations Reference area for per-integration detail.

Email transport (SMTP)

Per-site SMTP configuration — pairs with the Email and SMTP Reference.

Audit / activity preferences

Audit log retention, notification routing for operational events.

Operational toggles

Per-site toggles for site-level behavior (publish workflow rules, comment defaults, etc.).

Constraints and boundaries

Configuration is a Reference area for site-wide non-visual configuration.

Do not use for: visual configuration (Appearance), per-step procedures.

Public boundary

Public-safe.

Examples

Example 1 — Operator updates site name and tagline

Operator opens Site Identity, updates name + tagline. The change propagates to default meta titles, OG metadata, header brand text.

Example 2 — Operator configures SMTP

Operator opens Email / SMTP, enters SMTP credentials per Email and SMTP Reference, runs test. System mail and notifications now leave through the configured connection.

Example 3 — Operator tunes audit retention

Operator extends audit log retention from default to a longer window for compliance review needs.

Documentation guidance

Use this page as the structural definition for the Configuration pillar.

Reading order

Open when scoping site-wide non-visual configuration.

Related reading

• SG-Admin Overview — parent.
• Tools — sibling.
• Migration — sibling.
• Appearance — visual counterpart.

Vocabulary cross-reference

• Configuration pillar — non-visual site-wide configuration surfaces.
• Site identity — name, tagline, default OG image, contact.
• Operational toggles — per-site behavior toggles.

Maintenance discipline

When Configuration surfaces change across releases, update this Reference.

Related reading