External user privileges #5035
Unanswered
Emiliano75dg
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Hello, I suggest having templates that contain already the correct permissions. So in the Experiments templates, have the template "Experiment for project A", which already links to Project A AND has the correct permissions for it. This way, newly created experiments are already "correct". And you can force using templates to users, so they have to use one of the existing templates. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear all,
I am trying to configure an instance of ELABFTW to manage the experimental activities of a local node of a national research infrastructure. In this context, it would be useful to manage the privileges of external users who occasionally operate in the local node just to develop a single project.
At this moment I imagined that:
By doing so, I achieved that the external user is able to see and modify all and only the instances linked to the project, but only if whoever creates the project's resources and experiments manually modifies the visibility and writing privileges to include the group of the project external user.
I would like the full process to be automated. For example, when a resource or experiment connected to a specific project resource is created, the privileges associated with that resource should be automatically set up for all the other child resources connected to the parent one.
Is it currently possible to implement this function in ELABFTW?
Do I need to change drastically the architecture of my instance to realize this function?
Thanks in advance for any help
Best regards
Emiliano
Beta Was this translation helpful? Give feedback.
All reactions