Docs › Safety & account
Safety & permissions
An AI with access to your site needs guardrails. PressHelm was built around them: your rules, enforced on your own site, approvals, automatic rollback, and an emergency stop.
Your rules, per area#
In PressHelm → Settings → Permissions & security, set each area to default (reads and small safe changes run, changes ask), always ask (every change waits for you), or off (never). Your site enforces these itself, whatever the cloud sends.
| Area | Covers |
|---|---|
| Content | Posts, pages (incl. page-builder pages), forms, media and menus |
| Design | CSS, global styles, block templates |
| Settings | Site settings |
| Plugins | Installing, activating, updating and deleting plugins |
| Code | Theme and plugin files, child and draft themes, new plugins, code snippets |
| Database | Database rows and search-and-replace |
| Upkeep | Caches, permalinks, scheduled tasks |
| Store | WooCommerce products, orders, store settings |
| Others | Abilities of other plugins (Abilities API) |
Emergency stop#
One click in PressHelm → Settings → Stop & disconnect stops everything PressHelm does on your site, at once and whatever the cloud asks. Resume when you are ready. For hosts and developers, the constant PRESSHELM_EMERGENCY_STOP in wp-config.php does the same.
Built-in protections#
- Signed commands: every instruction to your site is signed and verified, in order, once.
- Encrypted vault: AI keys and bot tokens are encrypted in PressHelm Cloud, never stored on your site.
- Your bot answers only you, and approvals come only from you.
- Health checks and rollback after every change.
- Content is data, not orders: text from your site (comments, emails, pages) can never instruct PressHelm.
- Two-factor sign-in for your PressHelm account, in your dashboard.
Still stuck? Ask PressHelm itself in your chat, it knows this manual's tools, or write to hello@presshelmai.com. Last updated 2026-10-18.