I agree. A fair scattering of clients are very "iffy" about Cloud-based solutions. In addition, the providers of Cloud storage guarantee confidentiality - with a catch: some of the content they carry is outsourced to third parties that may not provide the same standards of confidentiality. I daresay this empty promise may also apply to some cloud- or network-based translation engines, and the service provided by them does not meet e.g. Swiss banking secrecy requirements. I hope you get plenty of approvals for our idea.

In Memsource, they have this Disable MT option. So what ha-ha... You can easily dodge this requirement by using apps like QTranslate for example. It allows you to apply a couple of dozens of translation engines and dictionaries from Google Translate to DeepL for free. All you need is just to assign a shortcut of your choice and select a translation engine. Whatever be blocked by such checkbox, the app would override it because it works in any text editor (including Studio's Editor and Export-for-bilingual-review docx files).

This is delivered partially with GroupShare, where users with "Translator" privileges by default cannot add translation providers. Would also be useful for file-based projects, however.