I’m building a new site for a client. I will be the Admin User, the client an Editor User. I’m writing an Editor Users Blueprint, setting up Permissions. The bit I don’t understand is the difference between the ‘user’ permissions and the ‘users’ permissions? They kind of sound like the same thing?
Here’s my blueprint (just the sections in question):
User permissions: What the user can do with their own account
Users permissions: What the user can do with regard to other user accounts
A non-admin user cannot create admin users, nor can they make themselves admins.
As far as I know you cannot allow/disallow based on role, so either a user can delete other users or not, regardless of their status, unless there is only one admin, which then cannot be deleted.
delete other users of all roles apart from the last/only admin user
change the email addresses of all users
change the password of all users
change the role of all non-admin users (doesn’t have an effect if there are only 2 roles)
I think it would make more sense to set changePassword/changeEmail users permissions to false, and allow users to reset their passwords (enable password reset in config).
Or you set these permissions to true, but use hooks to prevent this for admin users: Permissions | Kirby CMS
For anyone coming late to the party like me: There is an options parameter on users that allow to restrict exactly this, so that a non-admin user can’t change the password of an admin user.