Permissions to use AI Assistant are confusing
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3498873. -->
Reported by: [poker10](https://www.drupal.org/user/272316)
>>>
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>If you would like to add a permission to another role to use AI Assistant, you will probably go to permissions settings. There is only a <code>Access DeepChat API</code> permission, which will not allow usage for the other role.</p>
<p>In <code>/admin/config/ai/ai-assistant/drupal_agent_assistant</code> there is an Advance settings where you can allow other role. However this will only display chatbot for the role, but the communication will not work without the <code>Access DeepChat API</code> permission. </p>
<p>This seems to be confusing given the target audience of Drupal CMS. Can this be unified to one place? </p>
<h4 id="summary-steps-reproduce">Steps to reproduce</h4>
<p><strong>First scenario:</strong><br>
Create new user with content editor role<br>
As an admin, go to Drupal site permissions settings and add <code>Access DeepChat API</code> permission to the content editor role<br>
When logged in as a new user, observe that the AI assistant chat is still not displayed </p>
<p>---------</p>
<p><strong>Second scenario:</strong><br>
Create new user with content editor role<br>
Go to <code>/admin/config/ai/ai-assistant/drupal_agent_assistant</code> and allow content editor role to use the AI assistant<br>
When logged in as a new user, observe that the AI assistant chat is displayed, but when trying to use it, it will return an error (the reason is only in watchdog and it is a missing <code>Access DeepChat API</code> permission)</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Allow to make this settings on one place</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<h3 id="summary-ui-changes">User interface changes</h3>
<h3 id="summary-api-changes">API changes</h3>
<h3 id="summary-data-model-changes">Data model changes</h3>
issue