Skip to content
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

Remove publish rights for normal user #74

Open
Mijar007 opened this issue Dec 3, 2024 · 3 comments
Open

Remove publish rights for normal user #74

Mijar007 opened this issue Dec 3, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@Mijar007
Copy link

Mijar007 commented Dec 3, 2024

I noticed that normal users in a project have the "Publish to NFDI4Health GCHSH"-option. I think this option should be limited to project administrators and (maybe) asset gatekeepers.

@fmeineke fmeineke added the enhancement New feature or request label Dec 3, 2024
@fmeineke
Copy link
Collaborator

fmeineke commented Dec 3, 2024

Please specify what a "normal User" is for you. Now: If you have "edit" rights within project you are allowed to publish.

@Mijar007
Copy link
Author

Mijar007 commented Dec 4, 2024

I am using the terminology from the user guide. Therefore, it is someone with edit rights.
I thought a bit further and noticed what is missing: a sole passive project member.

From my point of view, it makes sense if all relevant project members are added to the project as a person. This improves the networking of people. At the same time, it is not necessarily desirable for everyone to be able to edit the metadata.
In this context, people without an account also represent a “risk”. If they do register with the LDH, they have direct editing and publication rights.
I therefore have three suggestions:

  1. Creation of the role of the passive project member.
  2. If the NFDI4Health PI currently has the rights of a normal user, change these to passive, since it is a representative role (Issue #65).
  3. The project admin could get access to a project-internal rights management. This could be used, for example, to set whether normal users are allowed to publish or whether changes made by normal users must first be approved by an asset gatekeeper before publication.

@Mijar007
Copy link
Author

Mijar007 commented Dec 6, 2024

For now I found a work around to create passive users: Add them and set them as inactive.
However, this makes it look like the member has left the project.
Bildschirmfoto 2024-12-06 um 10 45 53

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants