Agencies and client sites

If you build or run sites for other people, a team lets you share access to a site without handing over full ownership, group several sites under one client, and give your own agency's name to the pages your customers see.

Sharing a site with your team

Assign an existing site to a team from its card in Settings. Once assigned:

• Members can view and edit the site.
• Admins and the owner can additionally change its custom domain, roll it back, or delete it.
• Anyone outside the team sees nothing.

A team's hosting limit is shared across every site it owns - the limit scales up for Teams and Enterprise plans, so an agency running several client sites on one team gets more room than a single personal site would.

Clients

Group a team's sites (and any automated departments running them) under a client - a name, a contact, and a billing note. Each client's own guest can be given read-only access to just that client's sites, without joining the rest of the team (available on Enterprise).

Staging

Create a staging copy of a site to try changes safely before they go live. A staging site:

• Lives at its own address, always excluded from search engines.
• Is protected by a one-time password - share it with a client for a preview, without giving them a full account.
• Can be promoted to live with one click once you're happy with it, copying its published content into a new live version.

Cloning a site

Clone any site's currently published content into a brand new site - a fast way to start a new client from an existing design.

White label

Set your agency's name, logo, support email, and a primary color for a team. That identity appears on the generated pages your client's visitors see (like the privacy page) and on the public status badge, instead of the platform's own name.

Starter templates

Publish a site as a starter template - free or for a one-time price - so it can be cloned by anyone browsing the template gallery. A priced template splits the sale 80/20 in the author's favor; payouts to authors are handled by the operator rather than automatically.

An automated engineering department can be given permission to work on a site's staging version first and promote it once it looks right, and to propose sharing a site as a template - sharing always waits for a person to review and confirm it before it goes public.