Slack: Interesting discussion about options for controlling enty edit access
How Do I?
I’m wondering, when folks have really complex needs for controlling who can edit which entries (like, sometimes it’s two or three individials, sometimes it’s a group whose members change, etc., etc.), how do they handle it?
- With member roles only
- Through front-end editing and custom coding
- There’s some add-on that does this
- We just don’t…
Interested in learning more solutions or want to get to know other EE users? Read more about joining the slack here! Join Our Slack!
Several folks chimed in, with the consensus being… it depends!
From easiest to most complex: - Let the editors work this out themselves. - Native member Roles - Channel Form w/ Member Roles and/or conditional checks on member IDs to control access. - The Publisher plugin, if you also need publishing, review, etc.
Another user contributed a recent example where the site had regional chapters with editors being region specific. In this case, regions could be channels and editor role permissions allowed access only to their specific channel.
This was relatively clean because the role needs could be silo’d by region. It would be harder if the editing access had to be more intermingled
Thank you for informatiom! so useful