Restore permission for accessing AI Content Suggestion features

Open on Drupal.org →

Created on 9 January 2025, 27 days ago

Problem/Motivation

There is no way to manage access to the AI Content Suggestion features. The ai_content module included a permission "access ai content tools." When the module was converted to use plugins and renamed ai_content_suggestions, no permission was included.

Having a permission to control who can use those features is helpful. Since using AI adds costs, a site may want to limit which roles can use them. They also might want to limit to advanced editors, paid members, people who have agreed to terms, etc. Other AI modules (CKEditor, SEO, Image Alt Text) typically include a permission to allow access to the feature.

Steps to reproduce

1. Enable the AI Content Suggestions submodule.
2. Observe there is no link to "configure permissions" after enabling, as there often is.
3. Go to Configuration > AI Content Suggestion settings and enable some of the tools.
4. Edit a node and observe that any user can access the tools. There is no way to restrict access.

Proposed resolution

Add back a permission for "access ai content suggestion tools" and don't display the tools unless user has the permission.

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request

Status

Active

Version

1.0

Component

Other Submodules

Created by

🇺🇸United States heatherwoz Seattle

Live updates comments and jobs are added and updated live.

Sign in to follow issues

Merge Requests

!400Restore permission for accessing AI Content Suggestion features
Merged
🇧🇪Belgium wouters_f
updated 21 days ago

Comments & Activities

Issue created by @heatherwoz
Comment 26 days ago →
🇩🇪Germany marcus_johansson
Thank you Heather!

I was looking through the refactoring and its on me that this slipped through - the MR did remove it and I didn't review it correctly: https://git.drupalcode.org/project/ai/-/merge_requests/227

I will change this to a bug issue, since it was not removed on purpose, but a miss.

In the long run, I think we should actually set one permission per plugin, but that is out of scope for this.

@wouter_f - based on the Slack thread I'll assign it to you, if you don't have time reassign it to me and I'll fix it after Drupal CMS release.
First commit to issue fork.
Merge request !400re-add permission for this module → (Merged) created by wouters_f
Comment 23 days ago →
🇧🇪Belgium wouters_f Leuven
Comment 23 days ago →
🇬🇧United Kingdom seogow
Tested - the missing permision was restored.
Comment 21 days ago →
🇩🇪Germany marcus_johansson
Thanks you for the issue, for the changes and for the test. This is getting merged into the next patch release.
Comment 21 days ago →
🇺🇸United States heatherwoz Seattle
Thanks for fixing so quickly.
Comment 7 days ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024