Restrict acess in panel to certain pages within category

[texnixe]

It is also possible to use completely different blueprints on a role basis:

Custom blueprint for different roles

Hiya! I’m currently diving into Kirby 3 and loving it so far. For an online publication, I’ve set up two roles – admins who can edit everything and authors who should only be able to edit posts they’re the author of as well as create new blog posts. I’ve successfully used hooks to prevent anyone who isn’t an admin from updating any page he’s not the author of. However, instead of showing errors when someone tries to update a page without the necessary permissions, it would be more elegant to…

Permissions can set a role to change only specific pages?

There are two places where you can set page permissions: The user role blueprint, like the one you posted above. Those contain the general rules what a user role can or cannot do. You can set permissions on a per page blueprint basis (so not individual pages but pages with given blueprint). That means you can define what user role can read, edit, changeStatus of pages, see the docs: https://getkirby.com/docs/guide/users/permissions#specific-permissions-in-page-file-user-or-site-options On t…

User permisions for specific page and it's subpages

Ok, I just tested this and works perfectly for me. I disabled the default home.yml. Then in my plugin: <?php if(($user = kirby()->user()) && $user->role()->name() == 'client') { $dir = __DIR__. '/blueprints/client/home.yml'; } else { $dir = __DIR__ . '/blueprints/home.yml'; } Kirby::plugin('texnixe/permissions', [ 'blueprints' => [ 'pages/home' => $dir ] ]); And the structure of my plugins folder: [53]