As our Tulip user base grows, and our use of diverse Tulip functionality is growing, we are finding that the minimum browser-based user role, “Viewer”, is not restrictive enough.
Most non-operator users, such as supervisors, managers, engineers, planners, and other support staff are not app builders but require basic features, such as dashboard/analysis and adding their phone number for SMS functionality. However, there is no role, nor the ability to make a custom user role, that restricts only these basic functions.
The following are our concerns:
Stations - Viewers are able to see station details for active stations, who’s logged in, their player screen, paired interface
Connectors - Viewers can see all connectors and connector functions, including SQL queries exposing database, schema, and table names of external systems.
Edge Devices - Viewers can see IP addresses of Edge devices
Apps - Viewers can test apps, especially hidden or locked steps/functionality they couldn’t otherwise navigate to on a player. Viewers can see trigger configuration.
Interfaces - Viewers can see all interface details. (Count, device type)
Tables - Viewers can see all table data.
Ideally, my suggestion would be to add the “Cannot View” option to all of the categories/sub-categories of the custom user role creation options.
At a minimum, my suggestion would be to have a role which can distinguish between the non-development related functionality and the development functionality in the browser instance.