Skip to main content

How to restrict the AI Assistant to specific admin roles

The AI Assistant ships with an AI Assistant by Mirasvit permission that lets you control which admin roles can use the extension. This is useful when you want only certain team members to generate content with AI while other administrators keep working without the AI generate buttons on their edit pages.

Access is managed through Magento's standard user-role resources, at System -> Permissions -> User Roles.

1. Open the role you want to restrict​

Go to System -> Permissions -> User Roles and open the role you want to change (or press Add New Role to create one).

2. Switch to Role Resources​

Open the Role Resources tab and set Resource Access to Custom. The full resource tree becomes editable so you can grant or deny individual permissions.

note

Roles set to All (full-access roles) are always granted every resource, so they are unaffected by this permission and keep the AI generate buttons.

3. Grant or deny the AI Assistant permissions​

Locate the AI Assistant by Mirasvit node in the resource tree. It contains the following resources:

  • Use AI Assistant (show generate buttons) — controls whether the AI generate buttons appear on edit pages. When this is unchecked, the buttons no longer appear on any edit page for admins in this role.
  • Prompts — access to the Prompts management page.
  • System Messages — access to the System Messages page.
  • Automation Rules — access to the Automation Rules page.
  • Logs — access to the request logs.
  • History — access to the generation history.

To hide the AI generate buttons for a role, leave Use AI Assistant (show generate buttons) unchecked. To let the role use the Assistant, check it.

tip

The AI Assistant Settings permission that governs the configuration screen lives separately, under Stores -> Settings -> Configuration, so you can allow a role to use the Assistant without letting it change the extension's settings.

4. Save the role​

Press Save Role. Admins assigned to the role will see the change on their next page load — no cache refresh is required.