User / Role / Permission Management Thingworx - Best Practice
Dear everyone,
we are currently making our first steps with ThingWorx as an organization. We have version 8.5.0 of ThingWorx SCP Premium including Foundation, Asset Advisor, Connectivity and Application Building. So far we created some small applications via Mashups and we use the FactoryConsole as central entry point to our system (we added all custom apps also to the FactoryConsole).
We are facing massive challenges when it comes to efficient management of users, roles and permission, though. The system seems very complicated, especially when you want to change permissions for already created mashups etc, because permission settings are not inherited by a project or whatever (do I really need to change settings on each and every thing inside a project?!).
Basically, we only need two different user groups: one being the group of "Developers" that have access to the Composer and to everything else, except user and permissions management which is done by the Admins. The second user group we need is the group of "Viewing Users", that only have access to the FactoryConsole (NOT to the Composer) and are able to run and work with mashups / applications. In the best case, we'd also have a way of displaying only certain apps on the FactoryConsole for a certain group of users (i.e. maintenance apps for maintenance engineers), but this is actually the second step for us.
The question is, are there any best practices on how to implement a user structure like this efficiently? I just had the case where I added a user that should be a viewing user and it took me a lot of trial and error on the permission settings of different mashups, things and the like until I could verify that the user can use the considered mashup. However, he's also still able to access the composer (which he shouldn't be).
I hope that I could make my point clear, in case you need any additional information let me know. Would be great if someone has experience on this, I assume we cannot be the first organization facing these kind of challenges with TWX.
Thank you very much!
Kevin

