Disabling Studio in production environment

[Big Ring]

Simple question:

Can I disable Studio?

The reason behind the question:
When I deploy SugarCRM for a client I always have three environments -- Dev, Test and Prod. I never want any changes to be implemented in Test or Prod, rather, I want to develop every last detail and unit test in Dev before the client sees it in Test, etc. Recently I have had clients changing things in Prod (via Studio) and some of my custom code gets overwritten. While it is nice to hear from my clients, I would rather it not be because there is a crisis in production. Therefore, I would like to force them to make the changes in Dev and then promote the code.

First of all, am I being too controlling? Second, is there a better way than removing Studio? Third, am I writing bad code or using half-baked solutions if Studio is messing with some custom function?

I have not looked yet, but I am sure I can find the code that creates the link on the admin page and skip creating that link unless the environment is 'Dev', but I am just curious if there is a better way than "hacking" the core.

Any advice would be appreciated.

[arnaud_carrenet]

Hello Team,

as a only functionnal person I can't be of any help with Sugar code but what I can tell you is that your actions are good :
1 / Work with dev, test and prod environments
2 / In my company, we host 90% of our Sugar customers, we authorize our customers to "play" in the studio only if they have been trained to, some thing for dropdown lists and user admin.
3 / If we made some specific code that we want to prevent them to modify in the studio, then we redirect the studio page, for example, Account / Edit page will not be accessible while Account / Read could be depending on the code.
Hope this helps.

[Big Ring]

arnaud,
Thanks you for your insight. I had not thought of using redirects -- that is fairly brilliant. And it should be easy enough to manage in the controller.

[arnaud_carrenet]

Good if it helps ;-)