In D7 version of the module the permission hierarchy is as following:
Manipulate queues (Access the entityqueues list)
- User can see existing queues
Manipulate X queue (Access to update the X queue)
- User can see existing queues
- User can modify X queue
Manipulate all queues (Access to update all queues)
- User can see existing queues
- User can manipulate existing queues
Administer entityqueue (Administer entityqueue configuration and create, update and delete all queues)
- User can see existing queues
- User can manipulate existing queues
- User can create new queues
D8 version of the module behaves as following:
Manipulate queues (Access the entityqueues list)
- User can see existing queues
- User can create new queues (Bug)
Manipulate X queue (Access to update the X queue)
- User can see existing queues
- User can modify X queue
- User can create new queues (Bug)
Manipulate all queues (Access to update all queues)
- User can see existing queues
- User can manipulate existing queues
- User can create new queues (Bug)
Administer entityqueue (Administer entityqueue configuration and create, update and delete all queues)
- User can see existing queues
- User can manipulate existing queues
- User can create new queues
In addition, in D8 version Manipulate queues and above all see Configure and Disable actions on individual queues. However, these actions don't do anything.
Comment | File | Size | Author |
---|---|---|---|
#7 | 2856833-7.patch | 515 bytes | amateescu |
Comments
Comment #2
spesic CreditAttribution: spesic commentedComment #3
spesic CreditAttribution: spesic commentedComment #4
sassafrass CreditAttribution: sassafrass as a volunteer commented+1
Comment #5
amateescu CreditAttribution: amateescu for Pfizer, Inc. commentedThanks @spesic for such a detailed issue summary, it makes perfect sense to only allow users to create a queue only if they have the 'administer entityqueue' permission! Committed the patch attached to 8.x-1.x.
Comment #7
amateescu CreditAttribution: amateescu for Pfizer, Inc. commentedOops, not sure what happened to the patch uploaded in #5. Here's what was committed.