Block edits in experiments from template #4870
Replies: 4 comments
-
Hello Ivan 👋 What you expect is reasonable, and the argument about homogeneization is valid. But eLabFTW gives power to the researcher and doesn't enforce what you describe. Adding sub-permissions for particular actions, while a worthwhile long term goal (especially in the context of api keys permissions), isn't on the menu for now, so you'll have to let users do what they want with things they have write access to. |
Beta Was this translation helpful? Give feedback.
-
My suggestion would be to first solve this by policy and education. After all as the teamadmin you should have some "pull" on how to shape standards for your team. And maybe look at the api to automatically check for things that are important, and flag experiments that do not conform to that, email the owner etc... think about it like an experiment-linter of sorts. |
Beta Was this translation helpful? Give feedback.
-
Have a look at #4141 I think the table below could be expanded to all the things you can do on elab Profile 1
|
Beta Was this translation helpful? Give feedback.
-
@alexander-haller yes, indeed that's the only possibility left. But using the API and writing scripts to check that users don't do things they can do but shouldn't do is, well, involved. There's unfortunately only so much one can achieve through policy and education; there will always be users who just can't be bothered (because it takes time, because they forget, because "it doesn't work", because they don't understand, etc.) |
Beta Was this translation helpful? Give feedback.
-
As an admin, I can make sure that users cannot edit a template, but once the user creates the experiment from that template, he/she can delete/add/edit steps, extra fields, categories, linked resources etc. He/she can do pretty much anything.
From my perspective, it would make sense to have the possibility to block users from doing so, because if they do, it might break the consistency between the experiments. To me, this is the most important aspect of using a template: ensuring that the same information is recorded for every experiment following a given template.
Additionally, this implies that I would also like to be able to hide the JSON editor when users create an experiment from a template.
There might be settings I have missed somewhere. I searched for such a setting as admin and also asked the sysadmin to search for one, but we couldn't find anything relevant here. I couldn't find anything in the documentation or in the discussions either.
Or is there something I misunderstood? I am pretty new to eLabFTW, so maybe I am simply not using it "properly".
Beta Was this translation helpful? Give feedback.
All reactions