- 🇪🇸Spain juanolalla
> can you please write some steps to reproduce for this part?
"we have a bug with configure user don't have access to this page but still can see link on entityqueue list page"If a role doesn't get the permission "Administer entityqueue", but it does get the permission to "manipulate" the queue, then users with that role will see the "Configure" action for that queue, however, they can't access the corresponding page to configure it. They shouldn't see the "Configure" operation.
> Also, what's the use case for a separate enable/disable permission? Is the general "update" permission not sufficient?
Is not sufficient, because we could allow them just to edit the queue, so they can alter the order of the elements, add, edit, or delete those items. That doesn't imply configuration changes. However, with manipulate queue permission gives them the ability to "Disable" the queue itself, and we might not give them that permission, which actually does generates a configuration change which would imply a change in the config files and in the repository.