---
title: "List all settings"
method: GET
path: "/settings"
tags: ["Settings"]
---

# List all settings

`GET /settings`

Get the current value of all the settings

## Response `200`

Settings

- object
  - `result` 'success' | 'error', required — Result of the request
  - `action` 'getAllSettings', required — The id of the action
  - `data` object, required — Information about the setting
    - `settings` Settings, required
      - `allowed_networks` object[] — List of allowed networks for each policy server (root and relays)
        - `id` string — Rudder id of the policy server
        - `allowed_networks` string[] — List of allowed networks
      - `global_policy_mode` 'enforce' | 'audit' — Define the default setting for global policy mode
      - `global_policy_mode_overridable` boolean — Allow overrides on this default setting
      - `run_frequency` integer — Agent run schedule - time between agent runs (in minutes)
      - `first_run_hour` integer — First agent run time - hour
      - `first_run_minute` integer — First agent run time - minute
      - `splay_time` integer — Maximum delay after scheduled run time (random interval)
      - `modified_file_ttl` integer — Number of days to retain modified files
      - `output_file_ttl` integer — Number of days to retain agent output files
      - `require_time_synchronization` boolean — Require time synchronization between nodes and policy server
      - `relay_server_synchronization_method` 'classic' | 'rsync' | 'disabled' — Method used to synchronize data between server and relays, either "classic" (agent protocol, default), "rsync" (use rsync to synchronize, that you'll need to be manually set up), or "disabled" (use third party system to transmit data)
      - `relay_server_synchronize_policies` boolean — If **rsync** is set as a synchronization method, use rsync to synchronize policies between Rudder server and relays. If false, you'll have to synchronize policies yourself.
      - `relay_server_synchronize_shared_files` boolean — If **rsync** is set as a synchronization method, use rsync to synchronize shared files between Rudder server and relays. If false, you'll have to synchronize shared files yourself.
      - `rudder_report_protocol_default` 'HTTPS' | 'SYSLOG' — Default reporting protocol used
      - `reporting_mode` 'full-compliance' | 'changes-only' | 'reports-disabled' — Compliance reporting mode
      - `heartbeat_frequency` integer — Send heartbeat every heartbeat_frequency runs (only on **changes-only** compliance mode)
      - `enable_change_message` boolean — Enable change audit logs
      - `mandatory_change_message` boolean — Make message mandatory
      - `change_message_prompt` string — Explanation to display
      - `enable_change_request` boolean — Enable Change Requests
      - `enable_self_validation` boolean — Allow self validation
      - `enable_self_deployment` boolean — Allow self deployment
      - `display_recent_changes_graphs` boolean — Display changes graphs
      - `enable_javascript_directives` string — Enable script evaluation in Directives
      - `send_metrics` string — Send anonymous usage statistics
      - `node_accept_duplicated_hostname` boolean — Allow acceptation of a pending node when another one with the same hostname is already accepted
      - `node_onaccept_default_state` 'enabled' | 'ignored' | 'empty-policies' | 'initializing' | 'preparing-eol' — Set default state for node when they are accepted within Rudder
      - `node_onaccept_default_policyMode` 'default' | 'enforce' | 'audit' — Default policy mode for accepted node
      - `unexpected_unbound_var_values` boolean — Allows multiple reports for configuration based on a multivalued variable
      - `rudder_compute_changes` boolean — Compute list of changes (repaired reports) per rule
      - `rudder_generation_compute_dyngroups` boolean — Recompute all dynamic groups at the start of policy generation
      - `rudder_compute_dyngroups_max_parallelism` string — Set the parallelism to compute dynamic group, as a number of thread (i.e. 4), or a multiplicative of the number of core (x0.5)
      - `rudder_generation_max_parallelism` string — Set the policy generation parallelism, either as an number of thread (i.e. 4), or a multiplicative of the number of core (x0.5)
      - `rudder_generation_js_timeout` integer — Policy generation JS evaluation of directive parameter timeout in seconds
      - `rudder_generation_continue_on_error` boolean — Policy generation continues on error during NodeConfiguration evaluation
      - `rudder_generation_delay` string — Set a delay before starting policy generation, this will allow you to accumulate changes before they are deployed to Nodes, and can also lessen webapp resources needs. The value is a number followed by the time unit needed (seconds/s, minutes/m, hours/h ...), ie "5m" for 5 minutes
      - `rudder_generation_policy` string — Should policy generation be triggered automatically after a change (value 'all'), or should we wait until a manual launch (through api or UI, value 'onlyManual') or even no policy generation at all (value "none")

---

[API](https://skmtc.net/rudder/apis/rudder-api.md) · [All operations](https://skmtc.net/rudder/apis/rudder-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/rudder/rudder-api/versions/eab988254fba/schema)