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
We could use the OodSupport object to grab the groups for users to at least use some kind of logic in the views/files/index.html.erb file to check if the user belongs to the data-management group (or some such name) and render the button only if the user is in that group.
How to set the actual data-management group could maybe be done with the configuration_singleton by having some one group per site given this accepted role and checked, or maybe an array with many roles appended that is checked. Either way, the idea is to have users set the name of these groups at install with an ENV variable, then have that list checked in the view to render the button if a use is in the group.
Request
We've had some requests coming in to limit the ability to download and upload files in the files app based on groups:
This is a ticket to track how to do this.
Possible Solution
We could use the
OodSupport
object to grab the groups for users to at least use some kind of logic in theviews/files/index.html.erb
file to check if the user belongs to thedata-management
group (or some such name) and render the button only if the user is in that group.How to set the actual
data-management
group could maybe be done with theconfiguration_singleton
by having some one group per site given this accepted role and checked, or maybe an array with many roles appended that is checked. Either way, the idea is to have users set the name of these groups at install with anENV
variable, then have that list checked in theview
to render the button if a use is in the group.┆Issue is synchronized with this Asana task by Unito
The text was updated successfully, but these errors were encountered: