---
title: "Handing a site to a client | Briks"
url: https://briks.dev/docs/handing-over-to-a-client
description: "There is no handover button: you hand a workspace over by making your client its Owner. A walkthrough for agencies, with plans, credits and domains covered."
last_updated: 2026-10-08
---

# Handing a site to a client

When a site is finished, most agencies want the client to own it. Briks has no single handover button. You hand over the workspace the site lives in by making the client an Owner, then decide whether you stay on as an Admin or leave. This page walks through it, including where to build in the first place.

6 minute read Checked against the studio on 8 October 2026

## How handover works

In Briks a site belongs to a project, and a project belongs to a workspace. People do not own sites; they hold roles in workspaces. So handing a site over means giving your client the top role, Owner, in the workspace that holds it. Everything attached to the project comes along without being moved:

- the published site and every version of it;
- its domains, analytics, form messages and chatbot;
- the workspace's plan and its credit balance, which belong to the workspace and not to whoever set them up.

## Before you start: where to build

The easiest handover is one you plan for on day one. There are three ways to set it up.

| Set up | How it goes | Good to know |
| --- | --- | --- |
| A workspace you create for the client | Create a workspace named after the client, build there, invite the client as Owner at the end. | A new workspace starts with no credits (free credits come with your first workspace only), so it needs a paid plan before you can build in it. It counts towards the 10 workspaces you can own until you hand it over. |
| Build in your own workspace, move it later | Build with your agency's plan and credits, then move the project into the client's workspace when it is ready. | You need to be an Owner or Admin where it is now, and an Editor or above where it goes, which means the client invites you, on Pro or above. The client's plan must have room for another project. Credits already spent stay on your workspace's record. |
| The client's own workspace | The client creates an account, which comes with a workspace of their own, and invites you in as an Admin. | If it is their first workspace it comes with 50 free credits. Inviting you needs Pro or above on it. It does not count towards your 10. |

Mind the 10 workspace limit

One person can own up to 10 workspaces they created. Ones you hand over (the client made Owner, and you leave or take another role) stop counting, so the limit is about workspaces you still own.

## Walkthrough: hand over a finished site

This follows the first set up: a workspace you create for the client.

1. Create the client's workspace

   Where: Workspace switcher

   Click the workspace name at the top of the sidebar, choose **Create workspace** and name it after the client, such as `Leith Sourdough`. You are its Owner.

2. Put it on a plan

   Where: Billing

   A new workspace has no credits of its own, so building in it needs a paid plan. Switch to it, open **Billing**, press **Choose** on the plan it needs and pay at checkout. The client's own domain needs Starter or above. The plan does not need room for the client: inviting them as Owner at the end works on any plan.

3. Build and publish

   Where: Projects

   Start the project in this workspace, or move it in from your own (**Settings**, **General**, **Move project**). Publish it to production and connect the client's domain.

4. Invite the client as an Owner

   Where: Members

   Open **Members**, choose **Invite people**, enter the client's email and pick **Owner** under **Role**. Only an Owner sees that choice. Choose **Send invitation**. This works on any plan, even when the workspace has no room for more people, for one invitation as Owner at a time.

5. The client joins

   Where: Invitation email

   They open the link within 7 days. If they are new to Briks they create an account with that same address and confirm it from their inbox, then choose **Join**. They now show in **Members** as an Owner.

6. Decide your own role

   Where: Members

   Stay as an Owner, step down by picking **Admin** in the **Role** menu on your own row, or leave with **Leave workspace** from your row's ••• menu.

7. Settle who pays

   Where: Email

   A plan bought at checkout stays on the card of the person who paid, and only they can open **Payments and invoices**. Any Owner can still change or cancel it in **Billing**, and the payments keep going to that card. To move them to your client, write to hello@briks.dev before you step down.

Change your own role last

Once you are an Admin you cannot make yourself an Owner again; only an Owner can. Wait until the client has joined and shows as an Owner in **Members** before you step down or leave.

## Staying on as Admin, or leaving

| Your role after handover | You can | You cannot |
| --- | --- | --- |
| Owner | Do everything the client can. | Nothing is held back, which some clients will not want. |
| Admin | Build, change and publish, invite and manage Admins, Editors and Viewers, change settings and move projects. | Touch billing, make or remove Owners, or delete the workspace. |
| Editor | Build, change and publish, and connect domains. | Invite people, change the site's briks.live address or delete projects. |
| Left the workspace | Nothing. The client can invite you back while the plan has room. | See the projects at all. |

Many agencies stay on as an Admin while they look after the site, with the client as the only Owner. The client then holds the keys and can remove you whenever they choose.

## What happens to credits, the plan and domains

- **Credits** stay with the workspace. If you leave, the balance stays where it is and nothing comes back to you. If you moved the project in from your own workspace, the credits it spent before the move stay on your workspace's record.
- **The plan** is the workspace's, but its payments stay with the card that bought it. Write to hello@briks.dev about who pays for it from now on.
- **Domains** stay connected to the project. The records at the registrar do not change, and the domain stays registered wherever it was bought, so it is worth making sure the client owns that account.
- **Form messages, analytics and the chatbot** stay with the project.
- **Site email**, when it is switched on, still sends from the project's own address at `emails.briks.live`, not from the client's domain.

## What is not possible yet

- There is no one click handover button. Handover is the invite and role change above.
- There is no white-label dashboard, and white-label previews or reports are not available.
- Briks branding cannot be hidden. The invitation email, the sign-in page and the studio all carry the Briks name, and preview addresses end in briks.live.
- There is no reseller billing: no client sub-accounts with their own limits, no way to make your own plans and no margin on hosting.
- Emails cannot come from your agency's domain, and there is no custom login page.

Enterprise plans are set up with you. If you run many client sites, write to hello@briks.dev.

A handover in practice Ana's two person studio hands over a bakery site

> Ana builds the site for Leith Sourdough in her own studio workspace, where her Pro plan's credits are. When the owner, Callum, signs off, he creates his own Briks account, opens **Billing** in his new workspace and buys Pro at checkout, so he can invite Ana and connect his domain. He invites Ana as an Editor, and she moves the project into his workspace. Callum stays the Owner and makes Ana an Admin.

The site never went offline, Callum owns the workspace and its plan, the credits Ana spent while building stay on her studio's record, and the move did not use up one of Ana's 10 workspaces.

### Will the site go down during handover?

No. A project keeps its published site running while it moves between workspaces.

### Can the client remove me later?

Yes. An Owner can remove anyone, including other Owners. Your work stays in the workspace.

### One workspace holds sites for two clients. How do I hand over just one?

Move that project into a workspace of its own first, then hand that workspace over.

## Read next

- [Workspaces and account **Members and roles** Invite people by emailed link and give each one a role: Owner, Admin, Editor or Viewer. See what each role can do and how many people each plan holds.](https://briks.dev/docs/members-and-roles)
- [Workspaces and account **Workspaces** A workspace holds your projects, members, media, skills, plan and credits. Create one, switch between them, rename one and delete one you no longer need.](https://briks.dev/docs/workspaces)
- [Workspaces and account **Billing** See your plan and credits on the Billing page, buy a plan at checkout monthly or yearly, move up or down, cancel, and find your receipts and invoices.](https://briks.dev/docs/billing)
- [Publishing and domains **Connect your domain** Connect a domain you own to a Briks site: the three DNS records to add, how providers name them, what each status means and how to remove a domain.](https://briks.dev/docs/custom-domains)

Still stuck?

Write to [hello@briks.dev](mailto:hello@briks.dev) with your project's name and what you expected to see. A screenshot helps.