Glue42 Enterprise is now io.Connect Desktop! The new documentation site for all products is located at



Glue42 Enterprise is highly configurable. You can apply custom system-wide, as well as app-specific settings. Among the configurable features are system settings, app settings, Glue42 Windows, Glue42 Themes, logging and more.


The following JSON schemas describe the available options for configuring Glue42 Enterprise:

Note that a JSON schema for the logging configuration found in the logger.json file isn't available, as the Glue42 Enterprise logging mechanism is based on log4js-node. The logging configuration provided in the logger.json file is identical to the log4js-node configuration as described in the log4js-node API documentation.


All configuration files for Glue42 Enterprise can be found in %LocalAppData%\Tick42\GlueDesktop\config (mainly in the form of JSON files). There you can find the system.json file for system-wide configurations, the stickywindows.json file for configuring the default behavior of Glue42 Windows, the themes.json file for configuring the Glue42 Enterprise Themes, the channels.json file for configuring the Glue42 Channels, and the logger.json file for configuring the logging for Glue42 Enterprise.

In the \apps folder of the same directory, you can find the configuration files for the apps bundled with the Glue42 Enterprise installer.

You can add an app configuration file in the %LocalAppData%\Tick42\UserData\<ENV>-<REG>\apps folder to publish your own app locally. The <ENV>-<REG> placeholder should be replaced with the region and environment folder name used for the deployment of your Glue42 Enterprise copy - e.g., T42-DEMO. This way, your files won't be erased or overwritten, in case you decide to upgrade or change your Glue42 Enterprise version.

Note that the app configurations are monitored at runtime, so you don't need to restart Glue42 Enterprise when you change something. The location of the app configuration folder can be changed from the system.json. For more information, see the system.json configuration schema.