Reference → Integrations

Integrations

Connected third-party systems used across SGEN. This area defines how external services connect into the platform, where their effects appear, and what operational role they serve across the wider SGEN stack.

Definition

Integrations connect SGEN to external systems used for analytics, local visibility, communication, project handling, and payments. These pages document the platform role of each integration and where it appears, rather than acting as setup walkthroughs or support scripts. :contentReference[oaicite:0]{index=0}

Purpose

The purpose of this page is to define how external platforms enter the SGEN operating model. It establishes what connected services are for, where their downstream effects become visible, and how they should be interpreted as dependencies inside the platform.

Scope

This page covers integrations at the reference level. It does not provide step-by-step setup procedures or release-specific behavior. It defines connection role, visible product impact, and operational meaning across connected third-party services.

Defines how an external platform connects to SGEN.
Describes where connected data or controls appear in-product.
Clarifies the operational role of the connected service.

Responsibilities

The Integrations area is responsible for making external-service behavior legible inside the SGEN platform.

Connection mapping

Defines the relationship between an external system and the SGEN surface that receives, stores, or displays its data or controls.

Operational interpretation

Explains what role the connected service plays in analytics, communication, project handling, payments, or local business visibility.

Dependency clarity

Sets expectations around integration dependency, downstream visibility, and where connected behavior should become apparent in the platform.

Key elements

The Integrations section includes the following child pages:

Overview
Google Analytics 4
Google Business Profile
Google Search Console
ClickUp
Email and SMTP
Payment Gateways

Together, these pages define how integrations are organized and used across SGEN. :contentReference[oaicite:1]{index=1}

Operational role

Operationally, Integrations acts as the external dependency layer of the reference library. It explains how third-party platforms contribute data, service capability, or downstream behavior to SGEN, and how those contributions become visible inside the wider operating model.

Constraints and boundaries

This reference area defines integration role and visibility. It does not replace procedural setup guides, implementation-sensitive documentation, or release communication.

Use this area for reference definitions of connected services.
Use Guides for task-by-task connection or configuration instructions.
Use internal implementation documentation for connection internals or protected operational detail.
Use What’s New or Changelog for shipped changes to integration behavior.

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