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
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.
The text was updated successfully, but these errors were encountered:
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:
Creation of the role of the passive project member.
If the NFDI4Health PI currently has the rights of a normal user, change these to passive, since it is a representative role (Issue #65).
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.
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.
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.
The text was updated successfully, but these errors were encountered: