Documentation / Permissions and Safety

Permissions and Safety

Updated April 5, 2026

Safety by Default

Agent Builder is designed with a “read-only by default” approach. When you first activate an assistant, it can read your site content but cannot change anything without your explicit permission.

Agent Builder Approval Queue showing pending actions awaiting admin review
The Approval Queue — review and approve or reject pending assistant actions

Permission System

Each assistant has granular permissions you control:

  • Read posts/pages — View content on your site
  • Write posts/pages — Create or modify content
  • Read settings — View WordPress options
  • Write settings — Change WordPress options
  • Read files — View theme and plugin files
  • Write files — Modify theme and plugin files

All write permissions are off by default. Enable only what each assistant needs.

Approval Workflow

Even with write permissions enabled, sensitive actions go through an approval process:

  1. The assistant proposes a change (e.g., “Create a new blog post titled…”)
  2. You see exactly what will change, including a preview
  3. You approve or reject the proposed change
  4. If approved, the change is applied and backed up

Audit Log

Every action taken by every assistant is recorded in Agent Builder → Audit Log. This includes:

  • What action was requested
  • Which assistant performed it
  • When it happened
  • Whether it was approved, rejected, or read-only

Automatic Backups

Before an assistant modifies any file or database table, Agent Builder automatically saves a snapshot of the original. This covers posts, options, terms, metadata, robots.txt, llms.txt, and more.

Backups are stored in wp-content/agentic-backups/. Agent Builder keeps up to 3 snapshots per database table and restores in one click from Agentic → Approval Queue → Backups. Restoring also saves the current state first, so you can undo the undo.

See Backups and Restore for the full guide.

Browse all documentation →