Claude as your site's operator.

Staff ask, Claude prepares the change as drafts, a person reviews and publishes. These tools keep that loop simple and safe.

Requests

In Requests anyone with the section writes what they need changed – a title, the text, the page it is about and up to five attachments. Ask Claude to work through the open requests (the work_requests prompt): it prepares drafts, writes a note with links to them and marks the request done. The requester gets an e-mail with the note. A request never lets Claude publish or skip your confirmation.

Comments on drafts

In the builder, Share a draft and tick Allow comments. Whoever has the link clicks an element and writes a comment – no account. Comments appear in the builder under Comments; resolve them with one click. Claude can read and resolve them too.

Every change says why

Claude passes a short reason with each change – the request or what you asked for. The change log shows it next to the change.

Guardrails for Claude

In Settings → Extensions → Guardrails for Claude:

• Changes per connection and hour – a long run stops at the limit (0 = no limit).
• Deleting – switch it off and Claude cannot delete, trash or discard drafts; you do that in the admin.
• Protected pages – page numbers Claude must not change at all.

They hold for every connection on top of its access (read, drafts, full). When Claude hits one, it is told why and tells you.

Notebook

Notebook keeps notes for whoever works on the site next: decisions (“we never say cheap”), wording rules, photo credits, the history of a redesign, to-dos. Claude reads it before larger changes and writes decisions down; pinned notes are the first thing it sees. Notes travel with a site export.