IQSS / IQSS/dataverse

Feature Request/Idea: Add more granularity to roles permissions

Open
#9,190 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: Permissions Type: Suggestion User Role: Curator
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Overview of the Feature Request
Currently the role permission has 13 items which includes rights to add/edit/remove/view dataverses and datasets, manage datasets or dataverses permissions or download files. These authorizations are sometimes too broad, giving too many rights to employees who have been authorize.

What kind of user is the feature intended for?
Admin, Superuser

What inspired the request?
This request is a follow-up to the following discussion on Dataverse Google Groups: https://groups.google.com/g/dataverse-community/c/4VM49qUqMGo/m/_HhjaJtwBAA

What existing behavior do you want changed?
Some installations need more granularity in defining role permissions in order to better define those roles. Some permissions include other rights that can be abused by other users or that can result in undesirable behavior.

Any brand new behavior do you want to add to Dataverse?
Added more specific rights and extend the number of role permission to allow more complex workflow and prevent abuse and/or side effects.

Any related open or closed issues to this feature request?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or implementation entry points are named. Start by reviewing the linked Google Groups discussion and the current role-permission model; the work is done when the required additional rights and their intended boundaries are defined and implemented for more granular roles.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
authorization, backend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.