Plugin menu restrictions
Restricting which Aimogen Pro screens each WordPress role can reach, and how this differs from the Workspace setting.
System & Logs › Plugin Menu Restrictions hides plugin screens from specific roles, enforced server-side.
Rules are stored in aiomatic_Menu_Rules.
How it differs from Workspace#
| Workspace | Menu restrictions | |
|---|---|---|
| Scope | Per user, their own choice | Per role, set by an administrator |
| Purpose | Reduce clutter | Restrict access |
| Enforced | No — it hides the menu only | Yes |
| Bypassed by a direct URL | Yes | No |
Workspace is convenience. Menu restrictions are control. If you want a role kept out of a screen, this is the tool.
Configuring#
Each rule names a role and the screens it may not reach.
Screens that can be restricted are the plugin menus and submenus: Settings, AI Content Creators, AI Content Editor, AI Chatbot, AI Shortcodes & Forms, AI OmniBlocks, AI Agents, AI Embeddings, AI Model Training, AI Playground, AI MCP Integration, AI Snippets, AI Batch Requests, AI Assistants, More Features and System & Logs.
What to restrict#
Two screens are worth restricting before anything else, on any site with editors who are not administrators:
AI Playground. Unrestricted API access. Anyone who reaches it can make unlimited requests billed to you.
AI Agents. Anyone who can create an agent can give it any enabled tool and run it — including tools that modify content, query the database or send email. See Agent security.
Also worth considering:
| Screen | Why |
|---|---|
| Settings | Contains every API key in plain text fields |
| AI Snippets | Already requires manage_options, but restrict the menu too |
| System & Logs | Can display prompts and responses when detailed tracking is on |
| AI MCP Integration | Exposes the site to external clients |
A sensible model#
| Role | Access |
|---|---|
| Administrator | Everything |
| Editor | AI Content Creators, AI Content Editor, AI Shortcodes & Forms. Restricted from Settings, Agents, Playground, Snippets, MCP |
| Author | No plugin menus. Front-end tools with a credit allowance if needed |
This is not a substitute for capabilities#
Menu restrictions operate within the plugin. The stronger control is not granting
access_aiomatic_menu at all — a role without it sees nothing.
The capability is reconciled from Additional Roles under AI Usage Limits. See
Capabilities and roles.
Related#
Still stuck? Open a support ticket and include the diagnostics from Aimogen Pro › System & Logs › System Info.