> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/troubleshooting/interface/changing-system-labels-and-messages.md).

# Changing system labels and messages

Overriding the labels and messages shown in the OpenIAM interface, for English and for any other locale the deployment offers.

| Symptom                                                     | Likely cause                                                             | Resolution                  |
| ----------------------------------------------------------- | ------------------------------------------------------------------------ | --------------------------- |
| A label or message in the interface needs different wording | The shipped text is a default, and overrides are supplied per deployment | Override the one key, below |

Every label is a **key** and a **value** — the key identifies it, the value is what the user sees. You override a label by supplying a properties file with just the keys you want changed. There is no need to reproduce the whole set.

## Find the key

{% file src="/files/Lx73XjNolp2Gv0QRicdH" %}

Search the reference above for the text you see on screen and copy the key beside it. For the logout confirmation, `Are you sure you want to exit?` is `openiam.ui.shared.logout.warning.message`.

{% hint style="info" %}
This download is a point-in-time export and labels are added every release, so treat it as a way to find the key rather than as the authority. The `messages_en.properties` bundled with your own interface is the current set.
{% endhint %}

## Override it

The file is named for the locale — `messages_en.properties` for English, `messages_<locale>.properties` for anything else. Put only the keys you are changing in it:

{% code title="messages\_en.properties" %}

```properties
openiam.ui.shared.logout.warning.message=Do you want to exit?
```

{% endcode %}

{% tabs %}
{% tab title="RPM" %}
{% stepper %}
{% step %}
**Create the file** in `/usr/local/openiam/conf`, holding only the keys you are overriding.
{% endstep %}

{% step %}
**Restart the interface.**

```bash
systemctl restart openiam-ui
```

{% endstep %}
{% endstepper %}
{% endtab %}

{% tab title="Kubernetes" %}
{% stepper %}
{% step %}
**Create the file** where you can reach `kubectl` from, holding only the keys you are overriding.
{% endstep %}

{% step %}
**Make a ConfigMap from it** — see [Configure a Pod to use a ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/).
{% endstep %}

{% step %}
**Mount it into the interface StatefulSet**, in its `configmap` section, creating the section if it is not there.
{% endstep %}
{% endstepper %}
{% endtab %}
{% endtabs %}

Once the interface has restarted, the new wording appears in place of the default.

## Other languages

The procedure is identical — only the filename changes, to `messages_<locale>.properties`.

{% hint style="info" %}
**Take the locale code from the deployment rather than guessing it.** In the Webconsole, go to **Administration** → **Language**, select the language and read its **locale** field. Roughly eighteen locales ship, and the set grows, so that screen is the list for your release rather than anything written here. Japanese, for example, is `ja_JP`, giving `messages_ja_JP.properties`.
{% endhint %}

## Menu names

Menu labels are not in the properties files. Change them in the Webconsole under **Access control** → **Menus**: select the root menu, find the menu to change, right-click it, fill in the new values in **Edit menu**, and save both the menu and the tree. Restart the ESB — the container or the service — and the new label appears within about five minutes.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openiam.com/troubleshooting/interface/changing-system-labels-and-messages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.