> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/armor/settings.md).

# Settings

The **Settings** section holds two platform-wide admin stores: **System Settings** (arbitrary, typed configuration values) and **Global Secrets** (arbitrary name/value secrets available platform-wide).

## System Settings

A System Setting is a name/type/value entry — not a fixed list. A small set of known settings (e.g. a LangFuse observability URL) show up as ready-made templates, but admins can also define any custom setting a workspace or the platform needs to read.

Go to **AI Admin → Settings → System Settings**.

![System Settings, empty](/files/qPP9cBqJnRfSgoAPNpMS)

Click **+ Add** and fill in:

* **Type\*** — **String**, **Number**, **Bool**, or **JSON**
* **Setting\*** — pick one of the predefined settings, or **Custom Setting** to define your own
* **Name\*** — required for a custom setting; letters, numbers, `.`, `_`, `-` only
* **Value\*** — the input control matches the chosen Type (text field, number field, toggle, or a JSON editor)
* **Labels** (optional) — free-form tags for grouping related settings
* **Description** (optional)

![Add System Setting form, empty](/files/cVyzhZ00ePtJwfZDUCFe)

![Add System Setting form, filled in](/files/wUmQJC0HpG9wEuWoCF3R)

![System Setting added](/files/o7g5gzCFIm01E5fUq4ty)

{% hint style="info" %}
Settings created here are platform-wide (**Global** scope). A separate **Workspace Settings** page, available within a workspace's own settings, lets you define a same-named setting scoped to just that workspace — it overrides the global value for that workspace only, the same override pattern used by [LLM Mappings](/docs/armor/agents/llm-models.md#llm-mappings) and [Quotas](/docs/armor/access-control/quotas.md).
{% endhint %}

## Global Secrets

Global Secrets are name/value pairs available platform-wide — distinct from [Provider](/docs/armor/providers.md) credentials, which are tied to a specific cloud/tool integration. A Global Secret is just a value your agents can reference, merged in alongside any Workspace-, Project-, or Ticket-level secrets.

Go to **AI Admin → Settings → Global Secrets**.

![Global Secrets, empty](/files/7RduCHHj6GdsHRXwnEuV)

Click **+ Add** and fill in:

* **Key\*** — the secret's name; cannot be changed after creation
* **Value\*** — the secret value; hidden by default, with a show/hide toggle

![Add Secret form, empty](/files/XKQYTJ9dcxw2Qk9f42fP)

![Add Secret form, filled in](/files/ukz64l6UQdRc4nDj3PS6)

![Secret added, value masked](/files/a9t2yB1RzRzQh0C1rlyx)

{% hint style="info" %}
Once saved, a secret's value is always masked in the list and API responses — only the last few characters are shown. If a Workspace, Project, or Ticket defines a secret with the same key, that more specific value takes precedence over the Global one.
{% endhint %}


---

# 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://docs.duplocloud.com/docs/armor/settings.md?ask=<question>&goal=<endgoal>
```

`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.