> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/kmp/setup-luciq-for-kmp/custom-settings/user-identification.md).

# User Identification

Tie reports, crashes, and session replays from your KMP app to a known user with identifyUser, then clear that identity when the user logs out.

### Identify user

Associate the current session with a user (email, name, and optional ID). Use this after login or when you have user info:

{% code title="Kotlin" %}

```kotlin
LuciqKmp.identifyUser(
    email = "user@example.com",
    name = "Jane Doe",
    id = "user_123"  // optional
)
```

{% endcode %}

Reports, crashes, and session replays will be tied to this identity in the dashboard.

### Log out

When the user logs out of your app, clear their identity and data:

{% code title="Kotlin" %}

```kotlin
LuciqKmp.logOut()
```

{% endcode %}

Call this so the next user is not associated with the previous one.


---

# 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.luciq.ai/kmp/setup-luciq-for-kmp/custom-settings/user-identification.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.