Feature request: restrict Editors to specific content folders + show who made each edit
Hi Ben, Dan and team,
First, thanks for the Online Editor. It’s been a big step forward for the Dr Shen Tai Chi site (drshentaichi.co.uk), which I moved over from RW Classic. I’m on CMS Pro (originally Studio).
The site has a Teachers section with around 21 teacher profiles (growing to 30+ soon), each a Markdown file in a “Teacher Posts” content folder. I’d like each teacher to log in and keep their own profile up to date. Back on RW Classic I did this with Vibralogix access control, and it’s the main thing I’ve been waiting on Elements for.
I’ve set up individual Editor logins, but two things are holding me back:
- Restricting an Editor to specific content folders (or items)
At the moment the Editor role can create and edit posts in every content folder and manage every resource folder. I can’t see any way to limit a user to particular folders, and the user entries in the config only hold password, role and language. The Online Editor page on elementsplatform.com mentions giving an editor “access to their content folder only”, so I hoped this was possible.
What would help:
- a per-user (or per-group) setting to choose which content and resource folders an Editor can see and edit
- ideally, per-item ownership too (“Editor can only edit items they’re assigned to”), so many users could share one collection folder
Related question: if per-folder access is the route, does (or will) the Collection component read items from subfolders? That would let me give each teacher their own subfolder while the Teachers page still lists everyone from one Collection.
- Recording who made each change
I’ve connected the webhooks to Home Assistant, which works really well, but file.created / file.updated / file.deleted payloads only include the filename and folder index, and version history doesn’t show which user made a change either. With multiple editors there’s no way to tell who changed what.
What would help:
- include the acting user’s email (and role) in file.* webhook payloads
- show the user on each version history entry
With both of these I could safely hand the profiles over to the teachers. Without them, any teacher can edit every other teacher’s page and I can’t tell who did it.
Is either of these on the roadmap? Happy to test anything in beta.
Thanks,
Dave