Read-only by default
Every source connects read-only. Changes happen only on a source where an owner or admin chose Allow changes in Connections.
- Changes can be allowed on WordPress (with WooCommerce) and Google Analytics.
- Search Console, Magento and outside SEO data always stay read-only.
- Make read-only turns a source back to reading straight away.
Who allows and who approves
| Role | What they do | Changes through AI |
|---|---|---|
| Owner | Everything, including deleting the organization | Allows changes, asks for them and approves them |
| Admin | Manages members and connections | Allows changes, asks for them and approves them |
| Analyst | Views connections and uses AI | Read only |
| Member | Uses AI only | Read only |
What each change needs
Every tool has a risk class. It decides what happens when the AI assistant asks for it, once changes are allowed.
| Class | What happens | Who approves | Undo |
|---|---|---|---|
| Read | Nothing changes | Nobody | Nothing to undo |
| Draft | A draft, an image, a category: nothing visitors see | No approval | Yes, for 30 days |
| Edit | A change to a post, page or product | Nobody while it is a draft; an approval once it is live | Yes, the previous version is kept |
| Approve | Publishing, prices, stock, order status, refunds, settings, undo, new GA4 items | An owner or admin | Yes on WordPress, for 30 days |
| Confirm | Plugins on, off or updated, switching the theme, WordPress updates, search and replace across the database, administrators, switching code snippets on | An owner or admin, with an extra check: a 6-digit code in the chat, or their Mitos account password in the Mitos dashboard | Most yes; updates no |
| Classified | Users, snippet edits and more: the plugin's dry run decides what is needed | From no approval up to the extra check | Depends on the change |
Each tool's description names its class: Tools.
How an approval works
- Your AI assistant asks for the changeIn ChatGPT the Mitos approval panel opens right in the chat. In Claude it is coming soon; until then Claude gives you a link. Claude Code and Cursor ask with their own Allow prompt. If your organization has turned approvals in the chat off, your AI assistant gives you a link to the approval in Mitos instead. The Approvals page in Mitos also lists everything waiting, with a count beside the menu item.
- See what will changeThe approval shows the preview. On WordPress the site itself signs it: if the site changes before the change runs, it is refused and you are asked again.
- Approve or declineApprove or decline it. On the Mitos page the buttons are Approve & make the change and Decline. If you decline, nothing changes, and you can tell the AI assistant what to do instead.
- Carry on in the chatThe AI assistant carries on with the change within ten minutes. If it does not, tell it to go ahead.
A request nobody decides on expires and changes nothing. For many similar changes (the same action, on the same source, from the same AI assistant) you can also approve the next ones for 30 minutes, and each one is still listed on the Activity page.
The extra check for risky changes, and backups
Anything that affects the whole site or cannot be undone needs an extra check that it's really you, so a person, not the AI, confirms it after reading it once more. In the chat, where your organization allows it, you type a 6-digit code from your authenticator app or sent to your email. In the Mitos dashboard you confirm with your Mitos account password, never your website's. If you confirmed it a while ago you are asked again, and changes to a shop's customers ask for it again too.
- An owner can switch approvals in the chat off for the organization, or keep these risky changes in the Mitos dashboard only, under Settings.
- The preview of such a change says whether the site has a recent backup from its backup plugin.
- In wp-admin, under Tools → Mitos, the site's administrator decides whether that is only a warning or whether the change waits until a recent backup exists.
- The AI assistant checks with
wordpress_backup_statusand, with a supported backup plugin, starts a backup withwordpress_backup_now(also approved). - The built-in "Before a risky change" playbook does these in order.
Undo for 30 days
Every WordPress change is logged and can be undone for 30 days. Ask the AI assistant to undo a change: it lists them with wordpress_list_changes and undoes one with wordpress_undo_change. The undo is approved too.
- Cannot be undone: plugin, theme and WordPress updates (which is why a backup is suggested first).
- Cannot be undone: comments and spam deleted for good.
- Cannot be undone: emails already sent, such as an order note to a customer.
- Items created in Google Analytics stay until you archive them in Google Analytics yourself. Mitos deletes nothing there.
The log and personal data
- The Activity page in Mitos shows who changed what in the organization: sources, AI assistants, the team, and the changes AI assistants made.
- In wp-admin, under Tools → Mitos, Recent changes and Activity list every change Mitos made, in a log nobody can edit.
- Customers' names, emails, phone numbers and addresses are masked on the site before anything leaves it: WooCommerce customers, form entries, abandoned carts.
- Magento is the one source where the AI assistant can read customer names, emails and order history.
- Mitos does not record the questions asked or the data returned, and has no AI model of its own.
Everything Mitos keeps and does not keep: Security.