> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/support-application/sa-6/features/user-identity.md).

# User Identity

New in SA6 \*\*SA6 version introduced\*\*

#### Purpose

Displays who is currently logged in on the device and their identity-provider (IdP) connectivity/login status, plus a paginated history of past logins. This is a new feature in SA6 — SA5 has no working equivalent (see What's New in SA6). \<link to whats new>

#### Location

`ui/userIdentity/` (UserIdentityViewModel, UserIdentityScreen), `utils/IdpStatusHelper.kt`.

#### Responsibilities

* Read the current logged-in session (user id, username, roles, groups) from the BlueFletch Launcher via LauncherProviderHelper.getCurrentSession.
* Surface IdP connectivity/login status for the current session.
* Show paginated login history sourced from the local EventHistoryEntry table (the same local event-history store used by Advanced Tools's Database/Event Viewer).

#### Dependencies

* BlueFletch Launcher's ContentProvider (`LauncherProviderConstants.CONFIG_URI` family) — SA6 does not perform IdP authentication itself; it reads session state the Launcher already established.
* Local Room EventHistoryEntry table for history.

#### Troubleshooting

**Problem: User Identity screen shows no user / stale user.**

Check:&#x20;

1. Is the BlueFletch Launcher installed and running on the device?&#x20;
2. Is the Launcher's ContentProvider reachable (LauncherProviderHelper.getCurrentSession returning data)?&#x20;
3. Has the user actually completed login through the Launcher (vs. SA6 launched standalone without a Launcher session)?

\*\*need to check which version of auth and launcher provider exposes/returns user identity details&#x20;


---

# 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.bluefletch.com/bluefletch-enterprise/product-guides/support-application/sa-6/features/user-identity.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.