Access and approvals
You decide what each client may change.
Four levels of access, per client. What makes the site work stays protected. And when a client asks for more, it isn't refused: it waits for you.
Four levels
Per client, set when you invite them.
Choose a level when you invite a client, and change it any time. A shop owner who only updates prices and a marketing lead who builds landing pages can work on the same site, each with their own access.
Text and images
Words and pictures on existing pages. The default.
Blocks and pages
Also add, move and remove blocks, and add pages.
Design
Also colours, fonts, spacing and other styling.
Everything
Anything that is not protected.
Protected by default
What makes the site work stays yours.
Whatever the level, the parts that make the site work rather than what it says are protected. You can open them up per site.
Code stays code
In a component, a client may change the text and the styling, never the code itself. A script or an embedded frame is refused.
No broken links
An existing page can't be removed or renamed by a client, so no link to it stops working.
Checked twice
When a change is saved and again at Publish, on the change itself, not on what the assistant says it did.
Approvals
Above their level, it waits for you.
Your client can ask for anything. The assistant makes the change and they see it in their preview. When they publish, that part waits and the rest goes live. The owner of the site gets one mail per request, with the page before and after.
- Approve: it goes live through the same checks and build as any publish.
- Reject, with a note for your client if you like.
- I'll finish it myself: it leaves their draft, and you do it your way.
- When you approve, you can raise their level, so changes like this go live without you from now on.
Send to your builder
Bigger wishes reach you with everything you need.
Some things are about how the site works, like a contact form or the menu. When your client asks for one, the assistant explains that it's up to you, and with Send to your builder you get their request by mail.
Your team
Builders, owners, and an owner per site.
Builders in your team can open and edit every site of the team. Owners invite builders and handle the plan. Each site has its own owner, who decides on its requests.
- Unlimited clients and builders, on every plan.
- Activity on Home shows what happened on the team's sites.
- Each site's log shows who did what and when, in plain sentences.
Questions
Can my client break the site?
Not live. Code, forms and scripts are protected unless you open them up, a change above a client's access waits for you, and a change that doesn't build is never published. Anything that did go live comes back with Restore.
What does a new client get?
Text and images, unless you choose another level when you invite them. You can change it any time on the site's page.
Do builders need approval?
No. Builders in your team can edit every site of the team and aren't held to a level. Only the settings file stays protected in the editor, for everyone.
How many clients and builders can I add?
As many as you need. Unlimited clients and builders on every plan; plans count sites only.
Can I change what is protected?
Yes, per site, with protected and open in admin.json, the settings file in your repository.
In the docs
Step by step.
For builders
What your clients can change
The four steps, what is protected by default, and approvals.
For builders
Approvals
What happens when a client asks for more than their step, and how you decide.
For builders
Your team
Builders, owners, and the owner of each site.
More of the product: The editor · Publishing · Security · For clients
Hand it over. Get your evenings back.
Free for one site, forever. No card needed.