Skip to content

Insites AI · AI features in the admin

History and revert Beta

Last updated 18 November 2026

See every change the assistant proposed, and undo an applied one.

What History is for

Insites AI is pre-release. This page was written against the build of 12 November 2026 and will be revised at release.

Insites AI never writes on its own. Every change it makes to a page, partial, layout or record is recorded, and you can undo it. History is where you see all of them in one list. Use it to check what changed and who asked for it, and to revert a change that turned out wrong.

How a change happens

  1. You ask. For example, Rewrite the About page intro to sound warmer.
  2. It reads first. The assistant reads the current page or record, and the Insites Logic Engine rules for that kind of file.
  3. It proposes. A card shows a plain summary and a preview. Nothing has been written yet.
  4. You confirm or reject. Click Confirm to apply the change as yourself, or Reject to drop it. A proposal expires after ten minutes, and you then need to ask again.
  5. The page is checked. After a page change is applied, the site loads the page once. If the page shows an error, the change is put back automatically.

Only editors and owners can confirm a change. Everything an automation writes is recorded the same way.

Changes asked for in Slack or Teams

In Slack and Teams, only the person who asked can apply a proposal at first. That person can click Let others apply. The proposal then reads NAME asked. Anyone who can make changes can apply it., and any administrator whose AI role allows changes can apply or discard it. A viewer cannot. After the hand-over, the proposal lasts 24 hours.

The change records all three people. Open the change in AI > History to see who asked, who opened it to other administrators, and who applied it.

Open History

Go to AI in the main menu, then History. The page has two tabs.

Changes

Every change the assistant proposed, newest first. The columns are:

ColumnShows
WhenWhen it was proposed
TypePage, partial, layout, record, build or another kind of change
ModuleThe module the change belongs to
SourceWhere the change was asked for: Insites admin, Slack, Teams, Automation, Site assistant, API or Mobile app
ChangeA plain summary
StatusProposed, Applied, Reverted, Declined, Refused or Expired
CreditsWhat the applied change cost
AdministratorWho asked

Filter by date, status, type, administrator, module and source. The list shows the newest 1,000 changes in the period. Open a row to see the code difference, or the records before and after. From there you can view the page, open the conversation, or revert.

Conversations

Owners also see the conversations visitors had with the site assistant on your public site, marked Site visitor. See Site assistant.

Revert a change

  1. Go to AI > History and find the change. Filter by status Applied to narrow the list.
  2. Open the row and check the before and after.
  3. Click Revert. What was there before is restored.

If the assistant created the page, Revert deletes it. A page or form build reverts as one unit: every file it wrote is removed, newest first. You can also click Revert on the proposal card in the conversation. A change belongs to the administrator who made it, so only that person can revert it or open its conversation.

Revert does not need Git. The content from before the change is stored with the change itself.

If your team deploys from a repository

An applied change is written straight to the site, the same way as an edit in the admin. It does not reach your repository. Pull the change into the repository before your next deploy, or the deploy overwrites it.

Owners can switch on Write a Commit Message for Every Applied Change under AI > Configuration > General. Each applied change then carries a ready commit message with the question, who asked and the model.

Note

A change is charged when it is applied, not when it is proposed. Reverting a change does not refund it. See Credits, limits and pricing.

Related