Hierarchical user management

Hello Sandra,

I will show this idea to product management, but I have a problem with it myself. I would not be in favour of this. To explain my answer:

After 19 years in support for the Q-DAS software, I have seen it so many times that many users could configure many users or groups. And that always ended in chaos. If a superordinate user group, and every user in it, can now configure a subordinate user group, and every user in it, on demand, so to speak, then there is no longer any control at all. The Q-DAS software started out in the 32-bit version with just the configuration user, and every user was allowed to configure something. Over the years, group settings were added. Then came the option of removing the right for users to load their own configurations, because we realised how quickly a system can be reconfigured.

 Now, as a second-level-support, I am involved in many topics at customers, where I only have to clean up. And then explain the customers my “Best practise”: the group of system-administrators contains ONLY the 2 existing, ConfigurationUser and Superuser. A self created group called “Administrator” with specific Usernames for dedicated Users with a special Admin-Login are allowed to configure User groups. The groups are divided into “data collectors”, without the right to read own configurations, maybe “Supervisors” can have own configurations. But they are given to them in the Configuration-management, or they still have the right to configure themselves (own graphics needed for the communication with customers / suppliers, maybe.) And also, then the workshop to explain the Option of “Save configurations automatically”. That Users can test settings, but not save them.

I am abstaining from voting here because of my own statement.