Possibility to protect connections (and/or collections) from being changed
It is really comfortable and easy to copy, add and remove collections between multiple connections what we use a lot.
Most of them are test and development connections but sometimes one also uses a productive connection.
Because working with collections is that easy a user does not care the alerts anymore and just confirms or does not show them anymore.
I would like a possibility to prodtct specific connections from being changed at all (just readonly). This could also be done on collection level. This protection could be removed for rarely needed real changes.
Simon Berger
shared this idea
Hi, we now have a “Read-Only” lock to prevent this, and in preferences > general, you can have collections “read-only” by default too. Hope this helps!
You can also colour-code a connection to help remember which to avoid.
-
Simon Berger
commented
That setting is nice.
Would be even better per connection but that is helpful for a lot of users that need studio 3t just for reporting stuff. -
Simon Berger
commented
You added read-only collections. That's cool. But I can't think of many use cases for it (at least for my workflows), while whole read-only connections would be really helpful.
Could this be added on top to add an attribute to the connection and automatically (internally) mark all collections of a connection as read-only?