# Managing Client Sites

> Create and manage client sites (tenants) from one login - site intake, deploy status, white-label branding, and the agency layer.

Every client website in Seedly Sites is a **tenant**: its own pages, blog, media, settings, users, and Cloudflare Pages project, managed alongside all your other client sites from one operator login. This page covers creating sites, the per-site dashboard, and the white-label layer.

---

## Creating a Site

1. From the operator portal, click **+ Create new site**
2. Fill in the intake:

| Field | Description |
|-------|-------------|
| **Name** | The client's business name, shown across the portal |
| **Slug** | URL-safe identifier (for example `grantbrothers`) - used in portal URLs and the hosting project name |
| **Agency** | The agency this site belongs to |

3. Click **Create**

<DocShot src="/sites-docs-screens/create-site-intake.webp" alt="The Create a New Site intake form with site name, slug, brand color, and custom domain fields" />

Creating a site automatically provisions its own Cloudflare Pages project, so it is ready to [deploy](/docs/help/deploying) from day one. New sites also get starter legal pages (privacy policy and terms) seeded as editable pages.

There are two ways to fill a new site with content:

- **[Port an existing site](/docs/help/port-a-site)** - migrate the client's current website into the builder
- **Build in the builder** - start from [section presets and saved blocks](/docs/help/presets-saved-blocks)

---

## The Site List and Dashboard

The operator portal lists every site with its deploy status at a glance. Opening a site lands on its dashboard: pages, blog, media, analytics, settings, redirects, and the sidebar **Preview** and **Deploy** buttons.

Each site shows:

| Signal | Meaning |
|--------|---------|
| **Deploy status** | Pending / Building / Live / Failed |
| **Last deployed** | When the live site last shipped |
| **Custom domain** | The site's production domain, once set |

---

## The Agency Layer

Sites belong to an **agency** - the white-label parent that groups your client sites. The agency record carries:

| Field | Purpose |
|-------|---------|
| **Name + slug** | The agency identity |
| **Contact email / phone** | Agency contact details |
| **Logo** | Agency branding |
| **Primary color** | Agency brand color |
| **Max tenants** | Cap on how many sites the agency can hold (0 = unlimited) |
| **Active** | Agency account status |

For a single-agency install (the common case), you have one agency that owns everything. The layer exists so access can be scoped cleanly: users belong to an agency, sites belong to an agency, and nobody sees across that boundary except the operator.

---

## White-Label: What Clients See

The white-label story, stated honestly:

**What is branded:**

- **The login screen** - your logo and branding greet clients when they sign in, not ours
- **The published sites** - clean static output with **no "powered by" badge**, no builder watermark, nothing pointing back to the platform
- **Custom domains** - every client site lives on the client's own domain

**What is not branded:**

- The admin and editing interface itself is the platform's standard UI - it is not recolored per agency
- Email sender identity (password resets, invitations) is configured once for your whole instance, not per client

For most agencies this is exactly the right line: the client-visible surfaces (login, their website) carry your brand, and the working tools stay standard.

### Inviting a Client into Their Site

Create a user scoped to just their site with an appropriate role - typically Editor. They log in through the branded login screen and can only see and edit their own site. Roles and per-site access are covered in [Users and Roles](/docs/help/users-roles).

---

## Billing per Site

Each site can carry its own Stripe subscription (your client paying you), with per-site enforcement if payment lapses. See [Billing](/docs/help/billing).

---

## Summary

| Task | Where |
|------|-------|
| Create a client site | Operator portal, **+ Create new site** |
| Fill it with content | [Port a site](/docs/help/port-a-site) or build in the builder |
| Give the client access | [Users and Roles](/docs/help/users-roles) |
| Put it on their domain | [Hosting and Domains](/docs/help/hosting-domains) |
| Charge for it | [Billing](/docs/help/billing) |

---
Source: https://seedlysites.com/docs/help/tenants