It would be excellent if we could lock down some pages so that users can only edit specific pages, not the whole site. Maybe something on top of user groups?
For instance there could be default permissions, perhaps in user/config/admin/admin.yaml
(or maybe it would make more sense in blueprints, which allows setting this config depending on template):
# Only admins can delete pages
permissions:
pages:
write: [admin, editor]
delete: [admin]
And YAML config in each page could overwrite these default settings:
---
title: Awesome page
permissions:
write: [admin] # Limit changes to the admin group in the admin plugin
delete: [] # Protect this page from deletion from the admin plugin
---
I think a simple implementation could be limited to 2 permissions:
Excluding these other common permission types (less useful or harder to manage):
Some good ideas here. I actually already had a note with some ideas on how to improve permissions. I'll make sure this ticket is taken into account also. Thanks!
@rhukster Hey, just wanted to know if there is any progress on that topic that I missed?
For a specific project I need group-based edit-permissions for certain pages or pages of a folder. It's the only requirement that could potentially keep us from using Grav 😞
It would be really helpful, if you could point in the right direction, researching this.
Thanks a lot in advance for your help.
Most wanted feature!
bump
I have students who want to work on our school's website. Right now they are just passing me the information to post on the blog; it would be helpful to be able to give them access to specific pages so I don't have to worry about a student accidentally or purposefully editing the frontpage or something else important.
Thanks - hope that progress is being made on this feature!!
When can we aspect this feature. I hope so that it will be in the next version. :-))
@brianjschott You could checkout the Editable with SimpleMDE Plugin and test whether or not it suits your purpose. The latest version supports page based permissions using the Grav user and roles system. So you can create groups as well. Editing is limited to pages and in the frontend only.
I have to give editorial access to non-technical users, this would definitely help me sleep at night ! :+1:
Any progress on this? Most wanted feature.
I'm currently working on Flex Pages support and I already have permissions for deleting pages (though right now without owner support).
Some good ideas here. I actually already had a note with some ideas on how to improve permissions. I'll make sure this ticket is taken into account also. Thanks!
@rhukster over 3 years have passed from your comment. Some of my clients really want this feature, but we as Grav loving developers still have no info about it.
@mahagr What's the Flex Pages? It's about css flexbox or something different? Please give more info 😉
Flex Pages are based on Grav Flex Objects, which is just a cool name for the classes (you can find them in Grav\Framework\Flex
. :)
In short, Flex Objects will be replacing Flex Directory plugin; the core classes are in Grav itself, but for CRUD you will need the Flex Objects plugin, which will provide listing and editing views which will work in both admin and in the frontend Though that said, I am not sure if it will ship with working frontend editing or if you need to do some custom classes/routing to get it to work. Anyways, this plugin is only needed for admin tasks, Flex itself runs without it.
Flex Pages in implementation of the current Grav Pages, but based on these new Flex classes. Using Flex has a few benefits over the old solution:
FlexPage
is self-contained and much easier to use than Page
There are even more benefits, but we have been using these already in some of our projects and everyone is so excited about this. We get easily 10 times better performance on 4000-page site. We can create custom types, even pages that are stored separately from the regular pages and are in a separate section inside admin. Users can create their own pages by filling simple forms etc...
Thanks so much for sharing this info @mahagr 👍 Of everything you mention (it all sounds great!), more advanced page collections, page customization and separate Admin section for different page types are of most interest to me. Please add my vote for finer page permissions, that would be super valuable in educational scenarios with Grav!
Following this post. Badly need this right now.
I would really appreciate this function as well. Related to this open enhancement issue.
This has already been implemented in Grav 1.7 / Admin 1.10
Most helpful comment
Some good ideas here. I actually already had a note with some ideas on how to improve permissions. I'll make sure this ticket is taken into account also. Thanks!