- Issue created by @partdigital
- πΊπΈUnited States partdigital
I think one of the biggest issues we're are running into is that Taxonomy terms are a bit of a misfit for creating groups of users. They are great for categorizing content but miss some workflow features for handling users.
I had been considering a few approaches for this.
Access Policy Group module.
This is probably the most work but also has the most potential. For the sake of purity it might make sense to make it as another contrib module since Access Policy itself doesn't have much of an opinion.- It would be a new "Group" content entity type.
- It would very simple and share a lot of features with Taxonomy terms such as nesting and weights. It's essentially just another entity that access policy can talk to.
- You use it by adding entity reference fields to the Node and User like with taxonomy terms.
- The group would come with some operations like Manage members, Add member etc. These essentially are just forms for setting field values on the user.
- The Access Policy Group module would ship with its own access rules so in that way it can be more more prescriptive than taxonomy terms.
- The access part of this would already be mostly handled by access policy. This would primarily be a module with workflow enhancements.
- A new Group content entity type would clear the runway for features more geared to user enrollment.
Contribute to Views bulk edit
Using views to create group management pages could be very powerful. The main limitation is how to add members to that group from within that context. Perhaps Views bulk edit β could help?