# toolSettings This configuration section contains settings for the synchronization tool. The following example shows the available options within this section. ```javascript { ... "toolSettings": { "licensePath": "specsync.lic", "disableStats": false, "outputLevel": "normal", "parentConfig": "specsync-common.json", "ignoreParentConfig": false }, ... } ``` ## Settings | Setting | Description | Default | | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | | `licensePath` | Path for the license file. Can contain an absolute or a relative path to the config file folder. It may contain environment variables in `...%MYENV%...` form. Can be overridden by the `--license` [command line option](/specsync/jira/reference/command-line-reference.md#common-command-line-options). See [Licensing](/specsync/jira/licensing.md) for details. This setting is used for license files; use `license` setting for license keys. | `specsync.lic` | | `license` | The license key as a text string. This can also be loaded from an environment variable using the `{env:ENV_VAR}` syntax, or SpecSync will automatically load the license key from the `SPECSYNC_LICENSE_KEY` environment variable if available. Can be overridden by the `--license` [command line option](/specsync/jira/reference/command-line-reference.md#common-command-line-options). See [Licensing](/specsync/jira/licensing.md) for details. This setting is used for license keys; use `licensePath` setting for license files. | not specified | | `evaluationMode` | If set to true, SpecSync will not fail when the license scenario limit is reached but completes the synchronization up to the limit. | `false` | | `disableStats` | If set to true, SpecSync will not collect anonymous error diagnostics and statistics. Can be overridden by the `--disableStats` [command line option](/specsync/jira/reference/command-line-reference.md#common-command-line-options). | `false` | | `outputLevel` | Set the detail level of error messages and trace information displayed by the tool. Available options: `normal`, `verbose` and `debug`. Can be overridden by the `--verbose` [command line option](/specsync/jira/reference/command-line-reference.md#common-command-line-options). | `normal` | | `parentConfig` | Path for the parent config file. See [Hierarchical configuration files](/specsync/jira/features/general-features/hierarchical-configuration-files.md) for details. | not specified, the files in the parent folder will be considered | | `ignoreParentConfig` | If set to true, SpecSync will not apply the configuration settings of the config files in the parent folders or the user-specific configuration settings. See [Hierarchical configuration files](/specsync/jira/features/general-features/hierarchical-configuration-files.md) for details. | `false` | | `logFile` | Path for the log file to be created. Can be overridden by the `--log` [command line option](/specsync/jira/reference/command-line-reference.md#common-command-line-options). | no log file | | `allowDownloadingThirdPartyPlugins` | If set to true, SpecSync is allowed to download plugin packages created by 3rd parties from nuget.org or the specified package source. | `false` | | `pluginCacheFolder` | Custom plugin cache folder to be used by SpecSync to download plugin packages. | plugins stored in the SpecSync app data folder | | `disablePluginCache` | If set to true, SpecSync will always download or extract the plugin package even if the same plugin package version has been used already. This is useful for testing plugins. | `false` | | `plugins` | An array of [plugin configurations](#plugin-configuration). See [SpecSync Plugins](/specsync/jira/features/general-features/specsync-plugins.md) for details. | no plugins | | `suppressWarnings` | An array of warning codes that should be suppressed. Warning codes are displayed in the format `W####` (e.g. `W5113`). For example, `"suppressWarnings": ["W5113", "W5126"]`. | no warnings are suppressed | | `treatWarningsAsErrors` | If set to true, SpecSync will treat warnings as errors and fail the command when warnings occur. This provides greater security and ensures that warnings are addressed. Can be overridden by the `--treatWarningsAsErrors` [command line option](/specsync/jira/reference/command-line-reference.md#common-command-line-options). | `false` | | `forceProcessingRemovalsOnFilter` | If set to true, SpecSync will process removed local test cases (ie. add tag and remove from [remote scope](/specsync/jira/features/common-synchronization-features/remote-scope.md)), even if the synchronization is filtered. | `false` | ### Plugin configuration These settings can be used in the `toolSettings/plugins` array. See [SpecSync Plugins](/specsync/jira/features/general-features/specsync-plugins.md) for details. | Setting | Description | Default | | ---------------- | --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ | | `packageId` | The ID of the plugin package (NuGet) | either this or `assemblyPath` is mandatory | | `packageVersion` | The full version of the plugin package | mandatory, if `packageId` is specified | | `packageSource` | he package source (NuGet v3 feed or local folder) to be used to download the plugin package. | uses nuget.org feed | | `assemblyPath` | The path for the SpecSync plugin assembly (dll file) when the plugin is not loaded from NuGet package | either this or `packageId` is mandatory | | `parameters` | Optional parameters for the plugin in key-value pairs. Please contact the maintainer of the plugin for the specific values. | | {% content-ref url="/pages/As0iwTwtwwMJKOfZACmA" %} [Configuration reference](/specsync/jira/reference/configuration.md) {% endcontent-ref %} {% content-ref url="/pages/1LpjXDWvGNceAMRg0Z3o" %} [Hierarchical configuration files](/specsync/jira/features/general-features/hierarchical-configuration-files.md) {% endcontent-ref %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.specsolutions.eu/specsync/jira/reference/configuration/configuration-toolsettings.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.