Reference → Shared Concepts

Shared Concepts

Shared platform rules, models, and operating concepts used across SGEN. This page defines the common concepts that apply across major product surfaces and supporting system areas.

Definition

Shared Concepts in SGEN are the cross-platform rules, models, and operating ideas that remain consistent across SG Dashboard, SG Admin, SG Builder, workflows, automation, integrations, and migration-sensitive operations. This area exists to provide a stable conceptual layer for the wider platform rather than a description of one isolated surface.

Purpose

The purpose of this page is to establish the common terminology and platform logic that other reference areas depend on. It gives support, implementation, onboarding, and internal documentation a shared model for interpreting how the system behaves across multiple surfaces.

Scope

This page covers shared platform concepts at the reference level. It does not act as a procedural guide, screen walkthrough, or release note. It should be read as a conceptual reference for rules and models that appear repeatedly across the SGEN stack.

Defines rules and models that apply beyond a single product surface.
Provides a common language for interpreting platform behavior.
Supports consistent reading across Dashboard, Admin, Builder, workflows, automation, integrations, and migration-related references.

Responsibilities

The Shared Concepts area is responsible for keeping cross-platform understanding consistent.

Concept definition

Defines the shared models and operating ideas that appear across the wider SGEN platform.

Terminology alignment

Provides a stable vocabulary for support, implementation, onboarding, and product documentation.

Cross-surface consistency

Reduces interpretation drift when users move between Dashboard, Admin, Builder, workflows, and system-level reference areas.

Key elements

Shared Concepts typically covers platform-wide ideas such as ownership boundaries, cross-surface responsibility, system models, operational separation, and recurring rules that should not be redefined differently in every section.

Concept Family
Surface responsibility

Defines which platform surface owns account-level control, site administration, visual composition, or background behavior.

Concept Family
Operating models

Defines shared models such as site context, environment separation, structured administration, and platform-level flow continuity.

Concept Family
System relationships

Clarifies how major surfaces and supporting layers fit together as one governed platform rather than isolated tools.

Concept Family
Reference continuity

Provides the conceptual backbone that other reference pages can assume without restating the full platform model every time.

Operational Role

Operationally, Shared Concepts acts as the common interpretive layer of the SGEN reference library. It is the place readers should use when they need to understand how the platform thinks, how its surfaces are separated, and what recurring system rules remain true across multiple parts of the product.

Constraints And Boundaries

This page defines shared concepts at the system level. It does not replace surface-specific references, implementation notes, task instructions, or release communication.

Use this page for conceptual and model-level reference only.
Use section-level reference pages for specific surface ownership and module detail.
Use Guides for procedures and task execution.
Use What’s New or Changelog for shipped changes.

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.

On this page