-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editors get an error when creating users #1856
Comments
I'll try to run this down. They're not seeing the "role" dropdown because "change role" is a separate permission that they don't have. I'm thinking the reality here is that they've really never been able to do it, despite the manual and permissions being a little confused on the fact. |
Basically the situation is that Editors have never actually had the underlying permission needed to create users, though they do have the permission to see the add user page and therefore the button. My preference for fixing this would be to revoke that "page" permission and correct the documentation to match. |
I'd also rather that they do not see the page, rather than have the permission. |
Great. So, as far as discussion over the last few days/weeks, Supervisors are now
as per omeka/omeka-s-enduser/issues/127 . Editors are now
and lower level user roles are
which may or may not change if we do something re: #1855. |
I think that all sounds correct. |
Came up while doing #127.
Supervisors work as described.
Editors, who are supposed to be able to create users as per the manual, can click the "Add new user" button. But upon submission I get a "Forbidden" page.
So, either editors are supposed to be able to create users (if so - at what level(s)?), or editors shouldn't see the "Add new user" button, and I'll update the manual accordingly.
The add-user form doesn't have a role dropdown, so I'm not sure what the default role would be, were this to work. I am not sure if there is a good reason why an editor doesn't see the same add-user form as a supervisor (missing are the role dropdown, and the "is active" checkbox).
The text was updated successfully, but these errors were encountered: