> 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/signing-in/username_in_selfservice.md).

# Username not shown in SelfService

Showing a user their own account logins on the My Profile page in SelfService, which is off until an administrator adds the field.

| Symptom                                                                                  | Likely cause                                                                 | Resolution                      |
| ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | ------------------------------- |
| A user cannot see their own username, and **My Profile** in SelfService does not show it | The **My Identities** field is not among the fields configured for that page | [Add the field](#add-the-field) |

A user often does not know the login they hold in a target system, and has no way to look it up. The administrator can make those logins visible to everyone on their own **My Profile** page.

{% hint style="info" %}
**This is off in a new deployment, and always has been.** The field has never been part of the shipped default list, so nothing is broken — it has to be added once, by an administrator, for everybody.
{% endhint %}

## Add the field

{% stepper %}
{% step %}
**Open the setting.** In the Webconsole, go to **Administration** → **System Configuration** and select the **UI** tab.
{% endstep %}

{% step %}
**Add My Identities to Fields Shown on My Profile Page.**

The setting is a multi-select, so pick **My Identities** from its list rather than typing it; it joins the fields already there as another tag.

{% hint style="warning" %}
**Add to the list — do not clear it.** The setting cannot be left empty: the page refuses to build without at least one field and fails with `Key org.openiam.selfservice.my.info.fields produced no fields options`. Removing tags to "start clean" takes the whole page down, not just the fields you removed.
{% endhint %}
{% endstep %}

{% step %}
**Check it in SelfService.** **My Identities** now appears in the **My Information** panel on **My Profile**, with a **Show** button beside it.

Clicking **Show** opens a dialog listing the identities — the usernames the user holds in each system.
{% endstep %}
{% endstepper %}


---

# 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/signing-in/username_in_selfservice.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.