> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.10/troubleshoot-and-reference/reference/server-configurations.md). # Server configurations Cortex XSOAR provides custom server configuration settings that enable you to customize your Cortex XSOAR on the tenant level. You can also use custom server configuration settings in situations where you experience issues or need to troubleshoot situations in your environment. To modify or add server configurations: 1. Navigate to **Settings & Info** → **Settings** → **System** → **Server Settings** → **Server Configuration**. 2. Click **Add Server Configuration** or edit an existing configuration. 3. Enter the key and value. 4. Click **Save**. #### Engines | Key | Description | Default | | ------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | `engine.test.command.timeout``` |

Increases the timeout, in seconds, for a specific integration when using an engine. For example, change it to 300 seconds. Type in this format adding the brand name:

engine.test.command.timeoutTanium

| 60 | | `engines.notification.users` |

Specifies which users receive an email notification when an engine disconnects. A comma-separated list of Cortex XSOAR users. For example:

user1,user2,user3user1,user2,user3

| N/a | #### Google API | Key | Description | Default | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | `UI.google.api.key` | Entities that have Geo-location information (latitude and longitude) can be displayed on a Google map, by utilizing the Google Map API (which is required). For example, if you want to see the physical location of a computer that was attacked by Malware. To display the physical location of an entity on a map, run this command with the value: `Google Maps API` Key. For more information, see [Set up Google Maps in Cortex XSOAR to use map automations](https://xsoar.pan.dev/docs/reference/articles/google-maps). | N/a | #### Incidents | Key | Description | Default | | ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- | | `incident.closereasons` |

Customizes close reasons in a comma-separated list. For example:

false positive, resolved, duplicate, low priority, invalid, other

| `false positive, resolved, duplicate, other` | | `inline.edit.on.blur` |

By default, when editing the following inline values in an incident/indicator/threat intel report, the changes are not saved until you confirm your changes (clicking the checkmark icon in the value field).

These icons are designed to let you have an additional level of security before you make changes to the fields in incidents/indicators.

Set this configuration to true, to enable you to make changes to the inline fields without clicking the checkmark. The changes are automatically saved when clicking anywhere on the page or when navigating to another page. For text values, you can also click anywhere in the value field to edit.

| `false` | | `investigation.prevent.modify.closed` | Whether to add chats and notes to the closed investigation (set to `false` to allow). | `true` | | `module.health.notification.users` | List of names in CSV format to receive notifications when an integration experiences a fetch error. For more information, see [Receive notifications on an incident fetch error](/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/integrations/add-an-integration-instance/receive-notifications-on-an-incident-fetch-error.md). | N/a | | `Export.utf8bom` | Whether to export incidents and indicators to CSV using the UTF8-BOM format. For more information, see [Export an incident to CSV using the UTF8-BOM format](/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/incident-configuration/export-an-incident-to-csv-using-the-utf8-bom-format.md). | `False` | #### Indicators | Key | Description | Default | | ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | `enrichment.reputationScript.reliability` | The reliability of the score from a reputation script. | `A++` | | `indicator.timeline.auto.extract.enabled` | Enables the indicator timeline in the indicator extraction flow. For more information, see [Configure the indicator timeline](/cortex-xsoar-8-on-prem/8.10/investigate-and-respond-to-threats/threat-intel-management/indicator-configuration/configure-the-indicator-timeline.md). | `true` | | `indicator.timeline.enabled` | Enables the indicator timeline in all flows. For more information, see [Configure the indicator timeline](/cortex-xsoar-8-on-prem/8.10/investigate-and-respond-to-threats/threat-intel-management/indicator-configuration/configure-the-indicator-timeline.md). | `true` | #### Integrations | Key | Description | Default | | ------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | | `..timeout` | Timeout in minutes for specific integration commands. | `3` | | `sync.mirror.job.delay` | The interval for the job in minutes. For more information, see [Special Server Configurations](https://xsoar.pan.dev/docs/integrations/mirroring_integration#special-server-configurations). | `1` | | `sync.mirror.job.enable` | Enable or disable the mirroring job. For more information, see [Special Server Configurations](https://xsoar.pan.dev/docs/integrations/mirroring_integration#special-server-configurations). | `enable` | #### Notifications | Key | Description | Default | | ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | `content.notification.enabled` | Set to true to enable notification for new content updates. | `false` | | `content.notification.users` | Notifies all users by email when there is a content update available (comma-separated user names in Cortex XSOAR). | N/a | | `message.ignore.failedFetchIncidents` | Whether to ignore failed fetch incident messages. For more information, see [Receive notifications on an incident fetch error](/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/integrations/add-an-integration-instance/receive-notifications-on-an-incident-fetch-error.md). | `false` | | `message.ignore.incidentChanged` | Whether to disable notifications when an incident is changed. | `false` | | `message.ignore.incidentOpenedincidentOpened` | Whether to disable notifications, when an incident is opened. | `false` | | `message.ignore.incidentAssigned` | Whether to disable notifications when an incident is assigned. | `false` | | `message.ignore.investigationClosedinvestigationClosed` | Whether to disable notifications when an incident is closed. | `false` | | `module.health.notification.users` | List of names in CSV format. For example, **`user1,user2,user3`**. For more information, see [Receive notifications on an incident fetch error](/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/integrations/add-an-integration-instance/receive-notifications-on-an-incident-fetch-error.md). | N/a | | `server.notification.using.send-mail` | Select which email sender should send the notification. For more information, see . | | #### Playbooks | Key | Description | Default | | --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | `soc.name` | Customizes the SOC name in the survey header for an Ask task. For more information, see [Customize the SOC name](/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/playbooks/customize-your-playbook/customize-the-soc-name.md). | N/a | | `comm.ask.linktocontext.enabled` | Whether to display the links generated for an Ask task in the Context Data of the Work Plan. | `true` | | `comm. datacollection.linktocontext.disabled` | Whether to display the links generated for a Data Collection task in the Context Data of the Work Plan. | `true` | | `ignore.default.in.playbooks` | Whether to allow the \*\*Do Not Use By Default \*\*checkbox to affect playbooks. By default the Cortex XSOAR playbook does not take **Do not use by default** into account (only for CLI Commands). For example, if you have 3 mail sender instances, 2 of them are set to not use by default, when running the playbook without specifying an instance, it sends with all 3 instances. After you set this configuration to true, it only sends from the one that is not marked as do not use by default. | `false` | #### Proxy | Key | Description | Default | | ----------------------------- | ----------------------------------------------------------------------------------------------------------------- | ------- | | `condition.ask.external.link` | The address (including the HTTPS prefix) of the proxy used for external user communication in a conditional task. | N/a | #### Remote Repository | Key | Description | Default | | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | `UI.version.control.admin.only` |

Set to true to restrict access for pushing content to a remote repository to administators only.

Note

When set to true this key also removes the Save Version feature. This prevents users who don't have administration permissions from pushing content changes to the remote repository.

For more information, see Remote repository management.

| `false` | #### Reports | Key | Description | Default | | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | | `reports.time.zone` | Configure the timezone for widgets in a report. For more information, see [Configure the timezone in a report](/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/dashboards-and-reports/reports/configure-the-timezone-in-a-report.md). | Local time/Location | #### Scripts | Key | Description | Default | | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | `script.timeout` | The timeout, in minutes, to prevent blank pages when running a script. If you generate a report that runs a script and has blank pages you can Troubleshoot the script timeout. For more information, see [Troubleshoot script timeout for reports](/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/dashboards-and-reports/reports/troubleshoot-script-timeout-for-reports.md). | `3` | #### System Settings | Key | Description | Default | | ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | `UI.show.timezone.in.server.settings` | If set to true, settings for Keyboard Shortcuts, Timezone, and Timestamp format appear on the **Server Settings** page. By default, these settings instead appear on the **Preferences** tab of the **User Details** page. | `false` | #### SLA | Key | Description | Default | | -------------------- | ------------------------------ | ---------- | | `sla.risk.threshold` | Change the SLA risk threshold. | `72 hours` | #### Widgets | Key | Description | Default | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | `ROI.Cost.Monitor` | Amount in Dollars. Relevant for ROI widget. For more information, see [Saved By Dbot (ROI) Widget](/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/dashboards-and-reports/widgets/saved-by-dbot-roi-widget.md). | `60` | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.10/troubleshoot-and-reference/reference/server-configurations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.