-
Notifications
You must be signed in to change notification settings - Fork 20
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
Workbench Access per Page #3537
Comments
You can restrict pages not in the menu if you use a taxonomy scheme instead of a menu scheme. We also encountered issues where Workbench Access only works if you add the page to the menu using the "include menu link" checkbox from the node edit page, rather than through Structure > Menu. So instead of making editors manually change that for every page on the site, we opted for the taxonomy approach on our site too. Especially since taxonomy can be bulk applied from the Content overview page. We did not automate creation of taxonomy terms based on NetID, though, so this might not even be relevant to what you're requesting; but, in general, it is possible to restrict pages not in the menu. However, I think automatically creating taxonomy terms based on editors' NetIDs could potentially be a security and/or PII concern? Taxonomy pages are public by default, so it could potentially expose login usernames if visitors land on a taxonomy term page ( I can't remember if those taxonomy pages are set to not be crawled/indexed by Google or not, but unless the site has disabled those views or walled them off to editors only, they are reachable by anonymous users. Worst case, though, someone would have to get through CAS even if they were able to obtain a username via the taxonomy page. Using something like Rabbit Hole to wall off a specific taxonomy list and its terms to editors/admins only might get you around both of these concerns, though? |
Make taxonomy vocabulary "team" scoped rather than netID scoped |
Thanks Ashley! This is in line with some feedback I just received. The better intention on this is to create an "Editing Teams" taxonomy vocabulary so netIDs are not in any public format. |
See arizona.edu for example |
Motivation
I want to give users access to a page not in the menu
Is your feature request related to a problem? Please describe.
I cannot restrict editing to a particular page if it is not in the menu.
Proposed Resolution
Add a taxonomy vocabulary called “Users” and add that vocabulary to all content types
Describe the solution you'd like
Describe alternatives you've considered
Roles and Permissions considerations
A clear and concise description of how each of the following roles would be impacted by this change:
Anonymous user: No changeAuthenticated user: No changeContent administrator: No changeAdministrator: No changeAdditional context
The text was updated successfully, but these errors were encountered: