Claude and AI
Claude as your site's operator.
Ask Claude from the dashboard, requests from staff, comments on drafts, the reason of every change, guardrails for Claude and the agent notebook – all in the Claude part of the menu.

Ask Claude on the Dashboard: write what you need, Claude does it as drafts
Staff ask, Claude prepares the change as drafts, a person reviews and publishes. These tools keep that loop simple and safe. They live in the Claude group of the menu: Ask Claude and Claude settings, a hub with the tabs Settings and connections · Ask Claude · Scheduled runs · Notebook · Claude sessions.
Ask Claude from the dashboard
The Ask Claude box on the dashboard is the quickest way to hand Claude a job. Write what you need, as you would to a colleague, attach files if needed and press Send to Claude – it becomes a request (below), titled by its first sentence. Example requests under the box show what Claude can do; each person sees only those for the sections they may open. Click one, change it and send.
- Your requests lists your latest requests with their status.
- The box says whether a scheduled run works through the requests and when; without one, Claude reads them when someone asks it to.
- When Claude is not connected yet, the box says so, and an administrator gets a Connect Claude link.
- Copy for the Claude app copies your text with the site's address and opens Claude, for when you want to work with it right away.
The box is not a chat: Claude never runs on the site. It appears for people who may open Ask Claude when the Claude connection is on.
Requests
Under Claude → Ask Claude 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), or let a scheduled run do it: it prepares drafts, writes a note with links to them and marks the request done. The requester gets an e-mail with the note, and the finished request appears in Waiting for you on the Dashboard. A request never lets Claude publish or skip your confirmation.
A drafts only connection is enough for requests: besides drafts it may save hidden collection items, proposed exceptions to the opening hours, triage suggestions on enquiries and notebook entries. A change it may not make – a fact, a setting, a visible item – it writes into the note for a person to apply.
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 Claude → Claude settings, next to the Instructions for Claude, under 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 (a tab of Claude settings) 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 – a drafts-only connection too; pinned notes are the first thing it sees. Notes travel with a site export.

Claude → Ask Claude: every request with its status