-
Notifications
You must be signed in to change notification settings - Fork 134
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
Supervisor role cannot import new vocabulary #1857
Comments
I'd vote for
Edit in this context actually does make sense, since it means that you can change the language and label application. And also, reimport/update the vocab. There is, of course, a question of whether or not Vocabs actually have owners. |
So yeah just to get the lay of the land here, the actual rules in current usage explicitly deny the import page, and underlying create/update/delete for vocab objects, from the Supervisor role. Vocabularies do have owners recorded for them. |
Branch vocab-supervisor contains the fix here: it allows supervisors to do the import, and to update/remove only the vocabs they themselves imported. |
Can confirm that with Supervisor role, I can
|
No "Import new vocabulary" button. They also can't edit or delete.
If it's up in the air, I would vote to give them importing & editing but not deleting. Or maybe just editing their own vocabularies, not the base ones / ones installed by the global admins. The manual says:
which doesn't say anything about editing either.
The text was updated successfully, but these errors were encountered: