The existing “View Only” access for Table Queries and Aggregations in Tulip incorrectly gives users the ability to delete queries. This is a critical deviation from the expected “View Only” functionality, which should limit users to data viewing and testing, preventing any edits or deletions.
I discovered this while troubleshooting with a user who has “View Only” access for for Table Queries and Aggregations. During testing, I was able to delete queries. Because table queries are used in applications, their deletion can disrupt operations and compromise data integrity. Requesting the “View Only” role be updated to prevent users from both editing AND deleting table queries.
Screenshots from with View Role w/ “View Only” for Table Queries and Aggregations:
