How to restrict access to PROD env

[amith]

Hello,
It seems there are similar threads on this topic, and I am not sure how others are handling this scenario, as this seems very basic in terms of environment segregation between PROD and Staging/Sandbox.

Restrict Access By Environment

Hello, We recently began experimenting with building with retool and I quickly ran into a security issue that I can't seem to get past. Right now it seems access controls for retool plans only restrict based on application/component. As things stand, I'm unable to task our developers with creating tooling in a develop environment without exposing sensitive keys/secrets that would be needed by our production internal tools. If possible, it would be extremely useful to restrict access to envir…

Option to restrict access to production or staging API

We need to be able to control who has access to the data in our production database. Whilst still being able to allow some users to just have access to the staging environment. Our use case is as follows. We have an internal team based in the UK and they have access to the Live customer data. We also have a remote testing team. In order for them to test, they need access to our same internal tools. However, for data privacy reasons, we don’t want to grant them access to the production database…

No matter how careful developers can be, we really dont want them to inadvertently run any Update or Insert queries in our PROD database, while editing/creating an App.

How can we just restrict them to staging environment, and not even allow them to see the PROD instance of the db resource.

Thank you,