Workflows
Cross-product process flows that connect the SGEN stack. Workflows define how activity moves across product surfaces, system states, and operational handoff points instead of treating each surface as an isolated endpoint.
Definition
Workflows in SGEN are the cross-product process flows that connect the wider platform. They describe how actions, approvals, updates, and operational transitions move between surfaces such as SG-Dashboard, SG Admin, SG Builder, automation-aware processes, and integration-dependent states.
Purpose
The purpose of this page is to define workflows as a reference layer for platform continuity. It establishes how the system should be understood when work begins in one surface, continues in another, and produces downstream effects elsewhere in the stack.
Scope
This page covers workflows at the reference level. It does not function as a task guide or procedural walkthrough. Instead, it defines how process continuity should be understood across the SGEN platform.
Responsibilities
The Workflows area is responsible for making platform continuity explicit where one surface alone is not enough to explain what is happening.
Defines how activity moves from one product surface to another without breaking operational context.
Clarifies where responsibility shifts between dashboard control, site administration, visual editing, automation, or integrations.
Provides a reference model for workflows that involve multiple steps, multiple surfaces, or downstream system behavior.
Key elements
Workflow references typically center on process continuity, handoff logic, and the movement of state across the platform.
Defines where a workflow begins, such as a dashboard action, an administrative change, or an integration-aware event.
Defines where one surface stops owning the process and another surface or system layer takes over.
Defines what later states, dependent systems, or follow-on behaviors become relevant after the initial action.
Operational role
Operationally, Workflows acts as the connective reference layer of the platform. It explains how provisioning, content administration, builder activity, reporting behavior, integration-aware states, or recovery-sensitive operations fit together when the actual work spans more than one product area.
Constraints and boundaries
Workflows is a reference area for process structure and continuity. It should not be treated as a replacement for Guides, product surface definitions, or release communication.
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.