I was wondering if anyone had any examples of setting up users from inside a perspective application. We will be using the latest version once the project gets rolling. We are a large company and will have five different user access levels. We will have two main admins for the project, but would also like our various buildings on campus to be able to set up their own user access and alarm pipelines which we will call site admins. We also need to be able to get down to a system level on what the user will have access too( air compressors, cooling towers etc.).
We need to be able to give one user multiple security levels in different systems. Say engineer level on cooling towers but only operator level on air compressors.
So, if anyone has thoughts and/or examples about doing this from inside the application it would be great to see.
I searched through to see if this topic had been covered but didn't really see anything that fit. Apologies in advance if I missed it.
It is also a problem for anything requiring designer access (like creating/editiing alarm pipelines). While you can apply some security to designer operations, they are really just guardrails--any designer access is effectively full access to a gateway.
I completely understand your concern, unfortunately due to organizational requirements this will be necessary.
I appreciate the suggestion of that, I had started putting ideas down in power point and the results were similar but obviously a little more in depth to cater to our requirements.
Thank you, we are going to restrict this portion of the system to 7 people. Five of the admins will only be able to add users for their specific area. We are hoping to have predetermined alarm pipelines attached to the specific system so we can just add them in. Maybe all this set up information will be stored in a database not sure yet. I was mainly wondering if anyone had done anything like this before and if they had could they share an example or screen shot.