The DeepL for Windows app (app version 24.6.2 and later) can be configured from outside by IT admins. This is mostly possible for proxy settings at the moment.
Available admin settings
This is an overview of all possible settings an admin can configure outside of the DeepL for Windows app:
| Name | Type | Description | Since app version |
proxy.active |
Boolean | If set to true, the DeepL for Windows app is using proxy settings in general. The value true is mandatory if any other proxy settings are used. | 24.6.2 |
proxy.host |
Text | The host name of the proxy server. If no protocol scheme is given (e.g. http://), http:// scheme is assumed. Only used when proxy.active is set to true. | 24.6.2 |
proxy.port |
Numeric | Port number of the proxy server. Only positive integer values are allowed. Only used when proxy.active is set to true. | 24.6.2 |
proxy.activeCredentials |
Boolean | If set to true, the DeepL for Windows app is using proxy.username and proxy.password for proxy authentication (if provided). | 24.6.2 |
proxy.username |
Text | Username for proxy authentication. Only used when proxy.activeCredentials is set to true. | 24.6.2 |
proxy.password |
Text | Password for proxy authentication. Only used when proxy.activeCredentials is set to true. | 24.6.2 |
|
We also offer settings that allow you to enforce your team members to log in to the Windows app. This feature is available for Pro Business, Ultimate, and DeepL for Enterprise plans. Contact us to get more information.
| |||
If an admin configures any of those settings, the corresponding settings in the DeepL for Windows app will become inactive and grayed out. Now, the app user can’t change them anymore.
This way, admins may, for example, set proxy.activeCredentials to false to prevent users from adding a proxy username and/or password in their app’s settings under Advanced.
To provide more flexibility for admins, the proxy settings do not affect each other.
Configure admin settings
To give admins maximum flexibility, the DeepL for Windows app is looking for the settings mentioned above at different locations on the client’s device, ordered by descending priority:
-
Windows Registry of the local machine:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\DeepL SE
-
Windows Registry of the current user:
Computer\HKEY_CURRENT_USER\SOFTWARE\Policies\DeepL SE
- Environment variables
- Preferences inside the DeepL for Windows app:
This is the normal behavior for users when none of the above places are used. It is the same as in older DeepL for Windows app versions.
If a setting is found at one location, the setting is ignored at locations with lower priority. Different settings can be set at different locations, if needed. However, to avoid confusion, all settings should be placed at one location.
Settings via Windows registry
Via the Windows registry, admins can configure the above settings via simple key/value-pairs at:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\DeepL SE
Computer\HKEY_CURRENT_USER\SOFTWARE\Policies\DeepL SE
The keys and values always have the type string or text and are parsed by the DeepL for Windows app when the app is started. One example is the following proxy configuration using the Windows Registry Current Machine:
This example results in the following settings screen in the windows app (cannot be changed by the user):
Settings via environment variables
As an alternative to registering keys, admins can set environment variables. System environment variables have a higher priority than user environment variables.
To avoid naming issues, every setting for environment variables has the prefix DEEPL_APP_ and dots (“.”) are replaced with underscores (“_”).
For example:
DEEPL_APP_PROXY_ACTIVE
The values of these environment settings are all text and are the same as the registry variant.