> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/analyze/users-and-segments/audience/users/user-details.md).
# User details
## User details
Clicking any user row opens a **side panel** on the right with their full profile. The list stays visible underneath.
## It opens from anywhere there is a user list
This panel is not a feature of the Users page. It is the same panel everywhere Jimo shows you a list of people:
* the [Users](/docs/analyze/users-and-segments/audience/users.md) list, filtered or not
* the users behind a [segment](/docs/analyze/users-and-segments/audience/segments.md)
* the users reached by a specific experience, from its [analytics](/docs/analyze/analytics.md)
So the question "who is this person, actually?" always has the same answer, one click away, wherever you were looking. Nothing to navigate away from.
## Panel header
The top of the panel always shows:
* **Avatar** and **display name**, or **Anonymous** for unidentified users
* The **user ID** below the name. Click the copy icon next to it to copy the value.
* **Tags**, shown as coloured pills. If the user has none, a **Tag user** button appears instead. Either way, tagging happens here.
* A **...** menu, top-right, with **Delete user**.
{% hint style="warning" %}
Deleting a user permanently removes all their data from Jimo: attributes, activity, survey responses, segment membership. This cannot be undone.
{% endhint %}
## Navigation tabs
Three tabs organize the user's data.
{% tabs %}
{% tab title="Data" %}
The default tab: the user's snapshot. Activity summary, segment membership, attribute values.
**Metric cards**
| Card | What it shows |
| -------------------- | --------------------------------------------------------- |
| **First seen** | Date of the user's first session detected by Jimo |
| **Last seen** | Date of the most recent session |
| **Experiences seen** | Total number of Jimo experiences the user has encountered |
**User segments** shows every segment the user currently belongs to, as pills.
These update on their own. If the user stops matching a segment's conditions, the pill disappears without anyone doing anything. That is not a bug: a [segment is a definition, not a list](/docs/analyze/users-and-segments/audience/segments.md).
**Attributes** lists every attribute attached to the user, with a search field and three columns:
| Column | Description |
| ---------- | --------------------------------------------------- |
| **Name** | Attribute key: Jimer ID, Email, plan, role... |
| **Value** | Current value |
| **Source** | Where it comes from: Native, or an integration logo |
{% hint style="info" %}
For the full reference on attribute types, sources, and how to push each one, see [Attributes](/docs/analyze/users-and-segments/data-management/attributes.md). The **Adding user attributes in Jimo** link in the section header points to the same place.
{% endhint %}
{% hint style="info" %}
**Anonymous users show a nearly empty attribute table**, with little more than their auto-generated Jimer ID. That is expected: without identification, Jimo has nothing to attach beyond the session. See [Identify users](/docs/for-developers/for-developers/sdk-guides/identify-users.md).
{% endhint %}
{% endtab %}
{% tab title="Activity" %}
A chronological timeline of everything the user did with your Jimo experiences, grouped by day.
Each entry carries an icon for the experience type, what happened, which experience, and the time.
| Entry | What it means |
| ---------------------------- | ----------------------------------------------------------------------------- |
| **Viewed a hint** | The hint was displayed to them |
| **Viewed N Changelog posts** | Several posts read in one session, listed together rather than one entry each |
| **Completed all tour steps** | The tour was finished, marked with a green check |
| **Started a survey** | With a **View responses** shortcut straight to their answers |
| **Jimer XXXX was created!** | The very first time Jimo saw this person. The bottom of every timeline. |
The timeline reads most recent first. It is the fastest way to answer "what did this person actually see?" when a customer tells you an experience did not show up.
{% hint style="success" %}
**Use it as a debugging tool.** If a user says they never saw your tour, this timeline says whether Jimo showed it. An empty day usually means a targeting problem, not a rendering one. Pair it with the [Troubleshooting](/docs/settings/troubleshooting.md) tool.
{% endhint %}
{% endtab %}
{% tab title="Survey responses" %}
Everything the user answered in your [surveys](/docs/experiences/surveys.md), in two levels.
**The list.** One entry per survey they answered, with how long ago.
**The detail.** Click an entry and the answer is rendered **inside the step it came from**: the same NPS scale, the same options, with their choice highlighted.
That matters more than it looks: you read the answer with the question, in its original shape, instead of a value out of context. A 7 means nothing. A 7 on that scale, on that question, means something.
**See all users answers** jumps from this one person to the aggregate for the whole survey, when you want to know whether their answer is an outlier or the norm.
{% hint style="info" %}
To go the other way, from a pattern back to the people, use the **Answered with** condition in the [segment builder](/docs/analyze/users-and-segments/audience/segments/create-a-segment.md) to find everyone who answered a specific way.
{% endhint %}
{% endtab %}
{% endtabs %}
## Related pages
* [Users](/docs/analyze/users-and-segments/audience/users.md): the list this panel opens from
* [Filter users](/docs/analyze/users-and-segments/audience/users/filter-users.md): narrow the list before you open a profile
* [Attributes](/docs/analyze/users-and-segments/data-management/attributes.md): the reference for every attribute you see here
* [Tags](/docs/analyze/users-and-segments/data-management/tags.md): manual labels
* [Segments](/docs/analyze/users-and-segments/audience/segments.md): why segment pills appear and disappear on their own
* [Troubleshooting](/docs/settings/troubleshooting.md): debug why a user is or is not in the expected segment