Distribute consistent workspace configurations with push-to-client

Export a configuration file to a remote host for automatic distribution
Export configuration files to a host so that they can be automatically distributed to client development workbenches. You can export database connections, preferences, remote systems artifacts, editor templates, and snippets..

Change the remote host destination path of the configuration
You can change the default location on the remote host where a configuration is stored.

Import a configuration automatically when connecting to a remote host
If the administrator has exported a configuration to your server, when you connect to the server you will be prompted to apply the configuration to your workspace. If the force option was selected when the configuration was exported, if you do not accept the configuration, you will be disconnected from the server.

Export a configuration to your local file system
You can export configuration files locally to your file system. You can then send the configuration to a user so that they can then manually import it. You can also export a configuration locally as a way of backing up your database connections, preferences, remote systems artifacts, editor templates, and snippets..

Import a configuration from your local file system
You can manually import a configuration that someone has sent to you or that you have saved as a backup. Configurations can be used to standardize settings across an organization or as a method to copy database connections, preferences, remote systems artifacts, editor templates, and snippets. from an existing workspace into a new workspace.