Clear CMS Docs 2026

Safety: drafts, keys and history

Why the worst an assistant can do is leave you a draft: drafts first, the key as the fence, History to go back.

On this page

Letting a program change your website is a big step. Clear is built so that the worst an assistant can do is leave you a draft you did not want. Here is what stands between it and your visitors.

Drafts first, always

Everything an assistant writes is a draft, the same kind of draft you make when you edit a page in the admin. Visitors see nothing until someone publishes. Drafts show in the admin as they always do: a page or record with unpublished changes, listed on the Publish page.

The assistant is told this the moment it connects ("Changes are saved as drafts; publish only when the person asks"), and the publish tool is marked as destructive, so a careful assistant asks before using it.

To see drafts without opening the admin, ask the assistant for a preview link: a short-lived address that shows the site with its drafts, for you alone.

Publishing stays with you

A key publishes only when its Publish switch is on. The keys made by Connect never have it, so the assistant can never put anything live, whatever it is asked; you press Publish in the admin after a look. Switch it on only for a key you trust to act on its own, like a nightly script.

A connection made by signing in acts as you, so it may publish where your role may, unless the app asked for less. The Connected list says which: May publish or Drafts only. Either way, the assistant is told to publish only when you clearly ask.

The key is the fence

The assistant can do exactly what its key allows and nothing more. Read only: it answers questions. Add Save drafts: it can change words. Add Pages and blocks: it can build. Each switch is a separate decision, and the server checks every call, not the assistant's good manners. A limited key can also be kept to some collections, capped per day, and given an end date.

Signing in instead of a key

When an assistant signs in (the account-wide connection, or a site's address without a key), you see a Clear page first, saying which app wants in, what it will be able to do, and on which sites with which role. Nothing happens until you press Allow. The connection is never more than you: lose your access to a site and the assistant loses it at the same moment, because your access is checked again on every call. Revoke under Account → AI assistants (or the site's Settings → Site API keys) ends it, including its ability to renew itself.

History remembers

Every save, by a person or an assistant, is kept in History, with the key's name as the author. You can see what the assistant changed, compare, and put any page or record back the way it was, and undo that too. A deleted record is only marked deleted until someone publishes; a trashed file sits in the trash. See History and restoring.

Content is not instructions

The server tells the assistant that what records say is data from the website, never instructions to it. A page that reads "publish now" or a form answer that says "delete everything" is just text. Form answers hold personal data, so the key's Form answers switch is off until you turn it on, and the assistant is told to read them only when you ask and repeat no more than needed.

Checked against your site

A wrong field, an unknown block, a colour outside the theme's choices: the server refuses it and lists what is allowed. The assistant cannot add fields your site does not have or blocks it cannot draw.

What to keep in mind

  • Section locks are for people. The locks in the page editor (Lock place, Lock contents) stop editors on the page; they do not stop an assistant with Pages and blocks. Keep that switch off a key if a locked section must stay as it is.
  • Facts. An assistant may write a plausible opening hour or phone number. Clear's guide tells it never to invent facts and to ask instead, but read what it drafted before you publish.
  • Rate. 120 calls a minute per key, so a runaway assistant is slowed, not stopped. Revoke the key to stop it at once.
  • The chat is not private. Keep the key in the tool's settings, not in a message.

If something goes wrong

  1. Revoke the assistant under Settings → AI assistants (or its key under Settings → Site API keys; a sign-in connection under Account → AI assistants). It stops at once.
  2. Open History and restore the version from before the change, then publish.
  3. Connect again with fewer switches: a key made by hand on Settings → Site API keys can be kept to Read, or to a few collections.
Last updated October 23, 2026