---
title: "Hand over the site"
description: "Give the client accounts, roles and the Editor guide so they can onboard themselves."
requested_language: fr
language: en
translation_notice: "This page isn't translated yet"
url: https://docs.systhema.app/fr/guides/build-a-site/handover
version: unreleased (main)
docs_index: https://docs.systhema.app/fr/llms.txt
---
> This page isn't translated yet. Showing English.


## Goal

Give the client the access and instructions needed to run the site. The client onboards themselves with the [Editor guide](https://docs.systhema.app/fr/editor-guide.md), beginning with [Onboarding](https://docs.systhema.app/fr/editor-guide/onboarding.md).

## 1. Create named accounts

Create one account per person. Verify login and password reset with each intended role. Keep developer access with the agency; do not give a client `dev` because a narrower role is missing one capability.

Built-in roles include `dev`, `admin`, `editor` and `seoManager`. Review the [access-control reference](https://docs.systhema.app/fr/payload/access-control.md) before assigning them. Test publishing and user-management permissions with the actual account. Custom collections require explicit grants.

## 2. Prepare the handover record

Keep credentials in the client's approved password manager. Record who owns each service and where recovery instructions live.

```md title="client-handover.md"
# Northline handover

Site: production origin
Admin: production origin/admin
Site owner: named client contact
Editor accounts: individual names and assigned roles
Publishing owner: named account with verified publishing access
Password reset: tested date and sender address
Editor guide: shared link to the Editor guide and Onboarding
Services: domain, hosting, database, email and analytics owners
Backups: schedule, retention, restore owner and last restore test
Maintenance: agency contact, update process and support agreement
Credentials: password-manager locations, never passwords in this file
```

Share the actual published guide links with the client. In these docs, use [Editor guide](https://docs.systhema.app/fr/editor-guide.md) and [Onboarding](https://docs.systhema.app/fr/editor-guide/onboarding.md).

## 3. Let the client complete onboarding

Ask the client to sign in, read Onboarding and make a small draft edit. They should preview, save and publish using their own account if their role permits it.

Do not replace the guide with an agency-written manual for the standard editor. Add a short site-specific note only for custom blocks, content constraints or approval steps that the general guide cannot describe.

## 4. Prove routine operations

Ask the content owner to change a service paragraph, replace an image and submit the contact form. Confirm they can find the saved submission or that the notification reaches the responsible person.

Use a draft for practice. Check that the client understands which changes are live, which are drafts and who can publish. Confirm the rollback or restore contact before closing the project.

## 5. Record the installed version

```bash
node -p "require('./node_modules/@systhemaui/core/package.json').version"
systhema info
```

Keep the version and environment summary with the maintenance record, without credentials. The next developer uses it to choose version-matched documentation and upgrade notes.

## Check your work

- The client has named logins and tested roles.
- They received the Editor guide and Onboarding links.
- A client completed a draft-edit exercise themselves.
- Domain, hosting, database, media and email ownership are recorded.
- Backup recovery and future maintenance have named owners.

Next: use the [client-handover checklist](https://docs.systhema.app/fr/guides/recipes/client-handover-checklist.md) to close the handover, or choose a [recipe](https://docs.systhema.app/fr/guides/recipes.md) for the next change.