Guides → Site Provisioning Workflow

Site Provisioning Workflow

Field	Value
Audience	public
Page type	reference
Area	workflows
Updated	2026-05-14
What this covers
---
What is this for?
Good use cases
What NOT to use this for
How this connects to other features
Definition
Purpose
Scope
Entry surface
Handoff sequence
Downstream effects

How a new site is provisioned — Add Site at SG-Dashboard, configure in the admin, compose in SG-Builder.

Site Provisioning is the workflow that brings a new site into existence under an account. It begins at SG-Dashboard with the Add Site action, hands off to the admin once the site is provisioned, and routes into SG-Builder when the operator opens the homepage record for first composition. This page is the Reference definition of the site-provisioning workflow.

Site provisioning workflow — overview

Click "+ New Site"

→

Pick template

→

Configure domain

→

Site provisioned

What is this for?

Read this page when you want the structural definition of how a new site comes online — the entry surface, the handoff sequence, and the downstream effects.

Good use cases

You are scoping a new site rollout and need the full workflow path.
You are explaining to a stakeholder how SGEN provisioning works.
You hit a "where does the new site land?" question and want the model laid out.

What NOT to use this for

Step-by-step procedures — open the relevant Guide.
Per-release shipped change — open What's New or Changelog.
Per-component capability detail — open the corresponding surface Reference.

How this connects to other features

Workflows Overview — parent Reference area.
Publishing Workflow — sibling workflow that takes content live.
Content Update Workflow — sibling workflow for ongoing edits.
SG-Dashboard Overview — entry surface for the workflow.
SG-Admin Overview — first handoff destination.

Definition

The Site Provisioning Workflow is the cross-product process that creates a new site under an account, configures its initial state, and routes the operator into the surfaces that compose its first published content. The workflow involves three operating surfaces and one or two supporting layers (Workflows, Automation if scheduled health checks fire).

The defining property is multi-surface span. Provisioning is not a single-surface action; it crosses Dashboard, Admin, and Builder.

Purpose

The purpose of this page is to define site provisioning as a Reference layer. It explains the entry-surface / handoff-points / downstream-effects shape applied to the specific workflow.

Scope

This page covers the workflow at the Reference level.

The page covers:

The entry surface (SG-Dashboard Add Site).
The handoff to the admin once the site is provisioned.
The handoff to SG-Builder for first composition.
The downstream effects (site live at the assigned domain).

The page does not cover:

Step-by-step procedures — Guides.
Per-step Add Site UX — SG-Dashboard Site Manager Reference.
Per-release shipped change — What's New or Changelog.

Entry surface

SG-Dashboard → Site Manager → Add Site

The operator opens SG-Dashboard, clicks Site Manager, clicks Add Site. The Dashboard surfaces a setup flow for the new site (name, domain, plan capacity check). The provisioning event itself happens at this surface.

Entry points — where provisioning starts

SG-Dashboard — "+ New Site" button on portfolio view

Account onboarding — first-site wizard for new accounts

Migration — provision triggered by import workflow

Handoff sequence

Handoff 1 — Dashboard → SG-Admin

After provisioning completes, the operator routes into the new site's SG-Admin via the site card. The handoff is explicit (the operator clicks into the new site's card). At this point all site-tier work happens inside the admin.

Handoff 2 — the admin → SG-Builder

The operator opens the homepage record (or another initial editable record) and clicks Edit with SG Builder. SG-Builder loads in the active site context for first composition.

Handoffs — what's set up automatically

Staging URL assigned

Default theme + global colors

Owner role assigned to creator

SG-Admin / Builder ready

Audit log seeded

Backups auto-enabled

Workflow · Site provisioning

End-to-end timeline

SG-Dashboard

Entry

Add Site

Operator clicks Add Site, capacity checked, site provisioned.

→

SG-Admin

Handoff 1

Configure

Operator routes into new site, configures identity + settings.

→

SG-Builder

Handoff 2

Compose homepage

Operator opens homepage, clicks Edit with SG Builder, publishes.

Downstream effects

Site is live

After Handoff 2 concludes (homepage published), the site is reachable at its assigned domain. The provisioning workflow has ended.

Account state updated

Capacity used count increments by 1. The site appears in Site Manager card grid.

Per-site automation begins

Scheduled processes (daily backups, scheduled health checks) begin running for the new site.

Constraints and boundaries

This Reference covers the cross-product workflow. Per-surface detail lives in the surface References.

Use this Reference for:

Understanding the multi-surface provisioning sequence.
Routing operators or stakeholders to the correct surface at each step.
Reasoning about handoffs.

Do not use this Reference for:

Per-step Add Site UX — SG-Dashboard Site Manager.
Per-step composition — SG-Builder Reference + Guides.
Per-step settings configuration — SG-Admin Reference + Guides.

Public boundary

This page is intentionally public-safe.

Examples

Example 1 — New agency client onboarded

The agency operator provisions a new site under the client account, routes into the admin, configures site identity, opens homepage in SG-Builder, composes initial content, publishes. The full workflow takes one focused session.

Example 2 — Internal stakeholder spins up a site for an event

A stakeholder spins up a site for a one-time event. Same workflow, smaller scope. The Reference path is identical.

Example 3 — Migration prep using a fresh provisioned site

A site is provisioned as the migration target before content is imported. The provisioning workflow runs first; the migration workflow follows.

Documentation guidance

Use this page as the structural definition for the site-provisioning workflow. Procedural detail belongs in Guides; per-release behavior change belongs in What's New or Changelog.

Reading order

Open this page when scoping a new site rollout.

Vocabulary cross-reference

Provisioning is the act of creating a new site under an account.
Capacity check is the validation that the account's plan supports the new site.
Handoff is a moment in the workflow where ownership shifts between surfaces.
First composition is the initial SG-Builder session for the new site's homepage.

Maintenance discipline

When the provisioning workflow changes across releases (new step, new automation, new health check), update this Reference and log the change in Changelog.

Related reading

Topic
Workflows
Publishing Workflow
Content Update Workflow
SG-Dashboard
SG-Admin

Prerequisites

Before provisioning a new site:

Signed in to SG-Dashboard as Owner or Agency operator.
Available site capacity (e.g., 1/2 used means one slot remains).
Production domain known.
Access to your DNS host for A-record update.

Steps — Provision a new SGEN site

1. Open Sites

2. Click Add New Site

Enter the Production domain. Submit.

3. Tenant created

Success message: Tenant created successfully for . Staging usable immediately.

4. Point DNS

Add A record above. Wait 5-60 minutes for propagation.

5. Verify live

Visit Live Site + Login to Live become enabled once DNS resolves and SSL provisions.

Rollback / Recovery

Remove before public content — Site Manager → Settings → Delete Site.
Domain typo — Site Manager → Settings → Domain.
Capacity downgrade — contact support before next billing cycle.

Troubleshooting

"No available site slot" — at capacity. Upgrade or delete unused site.
Staging URL returns "Site not available" — wait 30-60 seconds. If still down, contact support with tenant ID.
Live URL never available — verify DNS resolves to 34.144.203.31. Give SSL 10-15 more minutes. Escalate if stuck.
Live actions stay greyed out — SSL pending. If > 30 minutes, escalate.

Where to find it

Open your SG-Admin and navigate via the sidebar group that owns this surface. For platform-level reference (this page), the entry point is the SGEN documentation index at docs.sgen.com. For the operator-facing configuration screen, the entry point is the corresponding SG-Admin module page linked in Related features above.

Reference shape

A minimal payload that this surface accepts or emits looks like:

{"site": "your-site.com","surface": "site-provisioning","actor": "operator@your-domain.com","timestamp": "2026-04-22T14:03:00Z"}

Use this shape when scripting against the surface or when reading audit logs that reference it.

Sample payloads

A provisioning request issued from SG-Dashboard:

{"request_id": "PROV-2026-00712","domain": "your-site.com","owner_email": "operator@your-domain.com","tier": "growth","site_template": "ecommerce-starter","requested_at": "2026-04-22T14:03:00Z"}

The provisioned site record emitted on success:

{"site_id": "site_8821","domain": "your-site.com","staging_url": "https://your-site.staging.sgen.com","live_url_pending_dns": true,"tenant_id": "ten_8821","provisioned_at": "2026-04-22T14:04:18Z"}

A failure state when capacity is exhausted:

request_id: PROV-2026-00713status: failedreason: no-available-site-slotrecovery: upgrade-or-archive-unused-site

On this page