> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/ugd-management/user-list/user-details.md).

# User Details

RealmJoin user details show a single user's profile, sign-in, devices, groups, app roles and software, plus runbooks, settings and effective RealmJoin roles.

This page shows detailed information about a single user object. Open it by clicking a user in the [user list](/ugd-management/user-list.md) or anywhere a user is linked in RealmJoin Portal.

The left side shows the user's core properties and stays visible in every tab. The right side shows the selected tab.

{% hint style="info" %}
Which tabs, sections and actions you see depends on your [role](/administration-and-settings/permission/pre-defined-roles.md) or [custom role permissions](/administration-and-settings/permission/custom-roles/available-permissions.md#user-management).
{% endhint %}

## User Summary

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2Fgit-blob-311842ce302351feea7359edbbcd5b96a4d8558c%2Fugd-user-summary.png?alt=media" alt="User summary with badges, creation date and directory properties"><figcaption><p>User summary</p></figcaption></figure>

### Status information

Badges and dates show the state of the user object:

* **Enabled** / **Disabled** - Whether the user can sign in. A disabled user also shows the note *Disabled in Azure AD* at the bottom of the summary.
* **Member** - The user is a native user in this tenant/organization
* **Guest** - This is an external user from a different organization
* **DE/US**... - Two letter code designating the user's [usage location](https://docs.microsoft.com/en-us/azure/active-directory/enterprise-users/licensing-groups-resolve-problems#usage-location-isnt-allowed) which is relevant for licensing.
* **Created** - Object creation date
* **Last activity** - The user's most recent sign-in (shown only if the user has signed in)

### Properties

Below the status, the summary lists the user's directory properties, if set:

* **Mail**, mobile phone (**M**) and business phone (**B**), and the preferred language. **NO MAILBOX** marks a user without a mail address.
* **First Name**, **Last Name**, **Job Title**, **Department**, **Office** and **UPN**
* **Manager**, linked to the manager's details page
* **Company** and the address (**Street**, **City**, **Postal code**, **State**, **Country**)
* **Entra ID** - The user's object ID. Click it to copy it to the clipboard.
* **On Premises Domain** - For users synchronized from Active Directory

### Last sign-in

If the user has signed in recently, the summary also shows details of the latest sign-in:

* **Last sign-in** - The application used, and whether the sign-in came from a browser or a client app
* **Cond. Access** - The Conditional Access result and the authentication requirement (for example single-factor or multifactor)
* **MFA Details** - The authentication method used, if any
* **Location** - City, region and country, derived from the sign-in IP address

## Overview Tab

The main tab. The **Sections** list on the left jumps to each section on the page. **External Links** open the user in the Intune admin center (**Intune Profile**) and in Microsoft Entra (**Sign Ins**, **Audit Log**).

### Devices

All Entra ID devices of the user, split into **Compliant Devices** and **Non-compliant Devices**. Each device shows:

* An **Entra** badge - highlighted when the device is Entra ID joined, dimmed when it is only Entra ID registered
* An **M** badge - highlighted when the device is managed by Intune
* The device name (linked to its [device details](/ugd-management/user-list/device-details.md)), operating system and version
* **Last Activity** - The approximate time of the device's last sign-in

### Groups and Teams

All groups the user is a member of, including memberships inherited through nested groups. Groups are bucketed by the RealmJoin group prefixes configured for your tenant (for example license, app or configuration groups); groups that match no prefix appear under **Other**. Teams-enabled groups are listed separately under **Teams**.

Each group shows three badges and its member count:

* **S** / **U** - Security group or Unified (Microsoft 365) group
* **S** / **D** - Static or dynamic membership
* **T** - Highlighted when the group is a Team

### App Roles

The enterprise application roles assigned to the user. **Access** shows whether the role is assigned **Direct** or through a group (linked).

### Proxy Addresses

The user's mail addresses (for example SMTP aliases), each with its address type. The primary address is shown in bold.

### RealmJoin software

Shown when [RealmJoin deployment](/application-management/deployment-methods.md) is enabled for your tenant. The section lists the user's devices with a number each, then a table of the software assigned to the user with the **Configured** version and one column per device.

Hover over a device cell to see its state, for example:

* *Up to date* (blue)
* *Outdated*, with whether Auto-Upgrade or Mandatory is set (red)
* *Failed n time(s) with last exit code c*
* *Installed, but not configured (anymore)*
* *Available to user, but not installed*
* *Not available for this device*

## Runbooks Tab

If you have been given Supporter or Admin permissions, this gives you access to runbooks that can be executed on this user object. For example to change an email address for a user.

Each runbook shows its description, recent runs and their status. Use **New Run** to start a runbook or **Schedule** to plan a run (if scheduling is enabled for that runbook).

See [Process Automation](/automation/runbooks.md) for more information.

## Self Service Tab

Shown when [Self Service Forms](/administration-and-settings/self-service-forms.md) are enabled for your tenant. It lists the forms this user has submitted, with the **Form**, the **Email** delivery status (for example *Sent* or *Rejected*), the **Webhook** result and when it was **Created**. Use **View** to see the submitted form.

## Settings Tab

You can assign Key-Value pairs of data to specific users to control RealmJoin Clients behavior for this user.

Most of the time this is used to overwrite settings configured on a group or for all users.

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2F3tobvrJ6pyWwGydcLYib%2Fimage.png?alt=media&amp;token=daa272a8-af46-4278-9302-36d1b828a089" alt=""><figcaption><p>Settings overview on a user</p></figcaption></figure>

You can add a setting assigned to this user using <img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FBtc1mXJyDJrHJhsFIdWm%2Fimage.png?alt=media&amp;token=cb7d14db-8138-4fe7-b492-a2cca63a5562" alt="" data-size="line">, alternatively open an existing setting by clicking on its name/key or search for a setting by name/key.

Clicking a name/key will open a UI allowing you to manipulate/create the setting.

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FkPeTwvuHWgbNPHypYGot%2Fimage.png?alt=media&amp;token=8c2f5480-bc9f-433e-a286-c95bf67b6afa" alt=""><figcaption><p>Setting editor</p></figcaption></figure>

Be aware: The value of the setting must be valid JSON, which includes singular values like `true` or strings (without brackets).

The switches in the lower half of the editor scope the setting to certain devices:

* **Only in VDI** / **Ignore in VDI** - Apply the setting only on, or never on, VDI devices (Windows 365, Azure Virtual Desktop)
* **Only on hybrid-joined devices** / **Ignore on hybrid-joined devices** - Apply the setting only on, or never on, hybrid-joined devices
* **Ignore on private devices** - Do not apply the setting on personal devices

Please see [Available Settings](/ugd-management/user-and-group-settings/additional-settings.md) for more information on which settings can be used.

## Roles & Policies Tab <a href="#roles-and-policies" id="roles-and-policies"></a>

Shows the RealmJoin Portal roles and permissions this user has. Use it to find out why a user cannot see or do something in the Portal.

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2Fgit-blob-661a64dd9437a41314439c6b8de22ed8d6dcd444%2Fugd-user-roles-policies.png?alt=media" alt="Roles and Policies tab with RealmJoin roles and policies"><figcaption><p>Roles &#x26; Policies tab</p></figcaption></figure>

* **RealmJoin Roles** - The [RealmJoin roles](/administration-and-settings/permission/pre-defined-roles.md) the user holds and how each is **Assigned via**: a group, an Entra ID role or an app role.
* **Policies** - Each [permission](/administration-and-settings/permission/custom-roles/available-permissions.md) with its **Status** (*Active* or *Inactive*) and the roles it is **Granted via**. A *Custom Role* badge marks permissions from a custom role, and *Blocked by condition* marks permissions whose conditions are not met. Turn off **Only active** to also see inactive permissions.

{% hint style="info" %}
Roles are evaluated as they would apply at the user's next sign-in. Eligible but not activated PIM roles are not included.
{% endhint %}

This tab is available to Admins and Auditors.

## Data Sources

The icons on the right of the tab bar show the raw [data sources](/ugd-management/user-group-device-management.md#data-sources) as JSON: **Entra ID Data**, **Sign-In Data** (the last 10 sign-ins) and **RealmJoin Data**. They are available to Admins, Advanced Supporters and Auditors when *Show advanced info* is enabled in [Settings](/administration-and-settings/general.md#show-advanced-info).


---

# 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.realmjoin.com/ugd-management/user-list/user-details.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.