Reference → SG-Builder

SG Admin

Site administration layer for content, modules, commerce, tools, and configuration. SG Admin is the structured administrative surface used to manage site records, settings, control panels, and operational behavior within the active site context.

Definition

SG Admin is the site administration layer in SGEN. It provides structured site administration for content, modules, commerce, utilities, and operational configuration. It owns record management, settings, and control panels that affect site behavior, and it works alongside SG Builder, which handles visual composition rather than administrative structure. :contentReference[oaicite:0]{index=0}

Purpose

The purpose of this page is to define SG Admin as the primary site-level administration surface in the SGEN platform. It establishes the types of administrative responsibility that belong here, clarifies how SG Admin differs from Dashboard and Builder, and provides a stable reference point for reading the rest of the SG Admin library.

Scope

This page covers SG Admin at the reference level. It does not attempt to document step-by-step operations for each module. Instead, it defines the administrative role, scope, and structural coverage of SG Admin as a whole.

Provides structured site administration for content, modules, commerce, utilities, and operational configuration.
Owns record management, settings, and control panels that affect site behavior.
Works alongside SG Builder, which handles visual composition rather than administrative structure.

Responsibilities

SG Admin is responsible for the administrative layer of an individual site. It concentrates operational control into a governed structure instead of scattering site management across unrelated surfaces.

Record administration

Owns inventories, detail views, creation flows, moderation surfaces, taxonomy management, and module-level records across site content and operational objects.

Settings and configuration

Owns site-level settings, defaults, policies, and control panels that influence downstream behavior rather than one isolated object only.

Operational visibility

Provides administrative visibility into the selected object type or module and serves as the entry point into follow-on tasks such as editing, publishing, moderation, reporting, migration, or configuration review.

Key elements

The SG Admin section includes a broad set of administrative areas. In the current reference library, these include the following top-level module families: :contentReference[oaicite:1]{index=1}

Overview
Dashboard
Appearance
Media Library
Blogs
Pages
Users
SEO
Discussions
My Forms
Phone Taps
Tracking Consent
Templates
Popups
Redirects
Custom Fields
Locations
Events
Analytics
Blacklist
Products
Orders
Coupons
Configuration
Custom Objects
Tools
Migration

Operational role

Operationally, SG Admin is the persistent system-of-record surface for site administration. It is where a site’s structured administrative state is created, reviewed, updated, and controlled. Inventory views, add-new surfaces, module settings, and configuration pages all exist here because they change site behavior in durable ways rather than providing temporary or portfolio-level visibility.

Constraints and boundaries

SG Admin is a site administration surface. It should not be treated as the portfolio control layer or as the primary visual composition environment.

Use SG Dashboard for account-level and multi-site operations.
Use SG Admin for record management, settings, and site-level administrative control.
Use SG Builder for layout composition and presentation editing.
Use Guides for procedural instruction rather than surface definition.

Documentation guidance

Use this page as a reference definition. Task-by-task instruction, onboarding steps, or procedural walkthroughs should live in Guides, while product updates and shipped changes should live in What’s New or Changelog. :contentReference[oaicite:3]{index=3}

On this page