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
Overview of the Feature Request
Splitting off a new ManagePrivateURL permission from the current ManageDatasetPermissions permission to manage Private URL and URLs for Anonymized Access
What kind of user is the feature intended for?
Dataverse collection or dataset administrators
What inspired the request?
Currently the ManageDatasetPermissions permission allows, in addition to managing dataset permissions, to manage Private URLs.
This has proven both confusing and limiting for installations:
Splitting a ManagePrivateURL from ManageDatasetPermissions would make the list of permissions clearer and allow installations to better adjust roles' permissions to their needs.
What existing behavior do you want changed?
Remove the ability to manage Private URLs and URLs for Anonymized Access in the ManageDatasetPermissions permission
Any brand new behavior do you want to add to Dataverse?
Add a new ManagePrivateURL permission with the following rights:
creating a private URL
disabling a private URL
creating an URL for Anonymized Access
disabling an URL for Anonymized Access
with the following description: "Manage Private URL or URL for Anonymized Access for a dataset"
Any open or closed issues related to this feature request?
Aforementioned issues on Permissions granularity:
Will you be able to contribute a Pull Request for this issue?
Yes, although it is not currently in our priorities for the coming month so feel free to start working on it if this is more urgent to your installation!
Thoughts for the future
For us, a distinction between Anonymized Private URLs (URL for Anonymized Access) and "regular" Private URLs is not currently a need, but it would be interesting to have other installations opinion on whether URL for Anonymized Access should, in the longer run, have a dedicated permission, separate from ManagePrivateURL or not.
The text was updated successfully, but these errors were encountered:
Overview of the Feature Request
Splitting off a new
ManagePrivateURL
permission from the currentManageDatasetPermissions
permission to manage Private URL and URLs for Anonymized AccessWhat kind of user is the feature intended for?
Dataverse collection or dataset administrators
What inspired the request?
Currently the
ManageDatasetPermissions
permission allows, in addition to managing dataset permissions, to manage Private URLs.This has proven both confusing and limiting for installations:
Splitting a
ManagePrivateURL
fromManageDatasetPermissions
would make the list of permissions clearer and allow installations to better adjust roles' permissions to their needs.What existing behavior do you want changed?
Remove the ability to manage Private URLs and URLs for Anonymized Access in the
ManageDatasetPermissions
permissionAny brand new behavior do you want to add to Dataverse?
Add a new
ManagePrivateURL
permission with the following rights:with the following description: "Manage Private URL or URL for Anonymized Access for a dataset"
Any open or closed issues related to this feature request?
Aforementioned issues on Permissions granularity:
and specifically Private URL (but broader):
Will you be able to contribute a Pull Request for this issue?
Yes, although it is not currently in our priorities for the coming month so feel free to start working on it if this is more urgent to your installation!
Thoughts for the future
For us, a distinction between Anonymized Private URLs (URL for Anonymized Access) and "regular" Private URLs is not currently a need, but it would be interesting to have other installations opinion on whether URL for Anonymized Access should, in the longer run, have a dedicated permission, separate from ManagePrivateURL or not.
The text was updated successfully, but these errors were encountered: