Skip to content

Insites AI · Credits and safety

How Insites AI handles your data Beta

Last updated 18 November 2026

Roles, data access, change control and keys for Insites AI.

What this page covers

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

This page explains the controls that decide who can use Insites AI, what it can read, and what it can change. Use it to set up access before your team starts, and to answer questions from people who look after your data.

Who can use the assistant

Only administrators of your site can use Insites AI. Each person is signed in as themselves, and their session lasts at most 24 hours. Every AI page in the admin checks that the visitor is an administrator.

Owners give each administrator one of three AI roles under AI > Configuration > Roles. The screen describes them like this:

Sets what each administrator can do with the assistant. Viewer: ask questions and read. Editor: also propose and confirm changes to records, pages and files. Owner: also change this configuration and the roles. An administrator who is not listed is an editor. If nobody is an owner yet, the administrator who saves becomes the owner. Give Viewer to people who should only look.

A person who is not an owner sees the configuration as read-only, with this message:

Your AI role is Viewer. Only an owner can change the configuration, so everything here is read-only.

The message names the person's own role, so an editor sees Editor in its place.

What the assistant can read

The assistant reads your data only through tools on your own site. Your site checks the person's role and your exclusions on every read, and refuses anything that is not allowed, whatever the assistant asks.

Owners control this on the Data Access tab under AI > Configuration:

  • Whole tables. Switch a table off and the assistant can no longer read or change it. Allow All and Exclude All change every table at once.
  • Fields in one table. Click Fields on a table and switch off the fields to hide, such as a notes field.
  • Fields on every table. Under Fields hidden on every table, add a field name such as email. That field is hidden in every table, including tables you allowed.
  • Sensitive Defaults hides email, phone, mobile and address fields on every table in one click.

For a hidden field, the assistant can still count and total records, but it never sees the values. The assistant can never read the private tables that modules keep for themselves, and that includes the private tables of the AI features.

Worked example: lock down a new site

You are the first owner. Your team includes a marketing assistant who should only look, and a developer who makes site changes.

  1. Go to AI > Configuration and open the Roles tab.
  2. Set the marketing assistant to Viewer and the developer to Editor. Leave yourself as Owner.
  3. Open the Data Access tab and click Sensitive Defaults.
  4. Use the Filter tables box to find any table that holds private data, such as staff records, and switch it off.
  5. Click Save.
  6. Ask the assistant a question about the excluded table. It should tell you the table is excluded.

See Choose what Insites AI can read for the full steps.

How changes are controlled

  • The assistant only proposes. A change is written only when an editor or owner clicks Confirm (or Apply for an automation), and it is recorded as that person.
  • Viewers cannot confirm. A viewer sees: Your AI role is Viewer, so you can read this proposal but not confirm it. Ask an editor or owner.
  • Every proposal is recorded in AI > History, with who asked, what changed and what happened to it.
  • Only the person who applied a change can revert it. Anyone else sees: This change belongs to another administrator, so only they can revert it or open its conversation.
  • A saved page is checked once for an error, and put back automatically if one appears.
  • Automations run without a confirm on each run, because a person confirmed the rule. An automation acts as the administrator who created it, and only that person or an owner can change it. Everything an automation writes appears in History.

Keys and connections

  • The site key is a random 48-character secret that lets the Insites AI service read this site's data and apply changes you confirm. It works for this site only and is never shown. An owner can click Regenerate Key on the Connection tab if the key may have leaked or a developer who had access has left. The old key stops working at once.
  • The AI model key lives only in the Insites AI service. It never reaches your site or the browser.
  • The site assistant key is public by design. It can only start a read-only visitor chat about your site.
  • Slack tokens are stored encrypted. Each Slack user is matched to an administrator by their profile email, and then has that administrator's role and limits.
  • Webhook triggers on automations accept a call only when it is signed with that automation's secret.
  • Private notes the assistant saves for you are visible only to you. You can read and delete them on the Memory tab.

Turning it off

An owner can switch the assistant off for everyone with the Assistant switch on the General tab. When it is off, the chat button and the AI pages are hidden and every request is refused. Settings are kept, so you can switch it back on later.

Automations have their own switch, under Automations > Configuration.

Limits

  • An excluded field is hidden from answers. Some module reads can still filter or sort on it, so exclude the whole table when its contents must stay private.
  • The assistant saves a private note without asking first. Review your notes on the Memory tab from time to time.

Troubleshooting

What you seeWhyWhat to do
Nothing on the Configuration page can be changedYou are not an ownerAsk an owner to change your role on the Roles tab
The assistant says it cannot read a tableThe table is excludedAsk an owner to allow it on the Data Access tab
You cannot click ConfirmYour role is ViewerAsk an editor or owner to confirm it
No Revert button on a changeSomeone else applied itAsk the person who applied it
The Connection tab shows Not ConnectedThe site key is missing or not registeredAn owner clicks Generate Key or Regenerate Key

Note

This page covers access controls only. For how credits limit spending, see Credits, limits and pricing.

Related