Hello,
As the number of apps grows, so does the number of developers and spreadsheets within the company. Furthermore, apprentices, for example, are also employed in app development. Since we now have tables with sensitive data in Tulip, it would be useful to have a way to make certain tables visible only to certain user groups.
Hello Fabian, thank you for bringing this up. We hear this request often, with many different variants.
Related to the table record visibility, would this apply to both app builders AND operators? In other words, app builders generally need to see table records in order to successfully test their apps. But, sometimes there needs to be restrictions on which app builders are able to view table records for the same reason as operators.
Hello Kevin,
I’m referring to app developers. In our case, app operators in general do not have access to tables. Some app developers only need access to the tables of their own apps. Currently, we have different plants in our workspace structure, and developers of other plants shouldn’t have access to all the tables of all plants.
Yeah, @kevin.kononenko while concepts similar to row level security would be great to have for operators. This functionality is very achievable through diligent app logic. However, there is no possible way to obscure confidential information from any user with admin access.
However, this is a tricky problem. Even if app developers can’t access the tables pages, they can actually access all data by just.. creating an app. As such, any secure solution would require some level of connection between app editor permissions and table permissions.
Understood. One clarifying question- does each individual plant have a workspace for itself? Or are there multiple plants in a single workspace? Would it be possible to have one plant per workspace?
We have individual workspaces for our locations. But all plants at a single location are located in one workspace, as they are partially connected with each other.