Skip to main content

Roles and permissions with MCP

What your Elovate user rights mean when you work through MCP, and why reading is open but deciding is not.

An AI assistant connected through MCP always acts as you. It can only do what your Elovate user is allowed to do. This article explains how that works.


Reading is open

Every user with MCP access can read the data of the connected environment: products, categories, attributes, workflow configurations, glossaries and every generated item, including items assigned to someone else. This lets you ask questions such as “are the translations waiting for review any good?” without being a moderator yourself.


Writing depends on your rights

Write tools, such as creating workflows, proposing changes or approving items, are only available when an Elovate administrator has granted them. They are managed under Settings → Users. If the assistant says a tool is not available to you, that is why.


Decisions follow assignments

For review decisions, only the assignment counts:

  • Editor: checks generated results, approves them or asks for a new generation.

  • Moderator: takes the final decision on editor-approved items.

Roles are set per action card. You can only act on items you are personally the editor or moderator of. This also applies to administrators: being an administrator in Elovate does not let you approve someone else's items through MCP.


What is never possible through MCP

  • Approving as moderator. This is the decision that leads to the sync, and it is made in Elovate.

  • Approving a proposal in the AI queue.

  • Syncing to the webshop.

  • Starting a workflow.


Confirmation for bigger actions

Every write takes an explicit list of items, never “all” or a filter. Actions on more than a few items return a preview first. Declining, rescheduling and re-running items always need a confirmation. The assistant shows you the preview and only continues after you confirm.

Did this answer your question?