You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Permissions Error when trying to switch contexts. Can the dropdown be hidden per user group? #138
When logging in as a publisher who only has access to a specific context, the "Choose Context" dropdown remains visible, but throws an error when trying to use it (see screenshot)
Also noticed, when logged in as a member of this same Publisher Group, my updates to the configurations are not being reflected.
Step to reproduce
Login as publisher
Go to Extras > Configuration
Click the "Choose Context" dropdown
Observed behavior
See screenshot above.
Expected behavior
The error makes sense, since the user does not have permission to access other contexts, but can this option be hidden from specific user groups/users altogether, so that they can never click on the dropdown and see the error?
Sounds reasonable. So either the user should only be able to switch through contexts he has permissions for, or either if it's a restricted user, then don't show the dropdown altogether – are these considerable solutions?
Just stumbled upon something maybe related, wanted to note it here:
For correct context-access (listing) the user-group needs a "AdministratorTemplate" with view_context here. I thought a "ContextTemplate"-access-policy with view there should be efficient, but it's not.
Activity
sebastian-marinescu commentedon May 22, 2018
Sounds reasonable. So either the user should only be able to switch through contexts he has permissions for, or either if it's a restricted user, then don't show the dropdown altogether – are these considerable solutions?
Mark-H commentedon Jun 26, 2018
Hm, I would expect in this case the context selector to still work, and be shown, but to only show the one context they have access to.
Can you check if your user has
view_contextpermission?sebastian-marinescu commentedon Jan 26, 2019
Just stumbled upon something maybe related, wanted to note it here:
For correct context-access (listing) the user-group needs a "AdministratorTemplate" with
view_contexthere. I thought a "ContextTemplate"-access-policy withviewthere should be efficient, but it's not.