> ## Documentation Index
> Fetch the complete documentation index at: https://interfere.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Users

> The people using your product, and session replays of what they did.

[Users](https://interfere.com/~/*/users) shows the people using your product and lets you watch what they did. When a problem comes in, you can see exactly who hit it and replay their session to understand how.

<img src="https://mintcdn.com/interfere/v8MNz-ve7d-NlcAv/images/user.png?fit=max&auto=format&n=v8MNz-ve7d-NlcAv&q=85&s=79ee747c15634ad5adc9903c50666912" alt="User profile showing traits, active problems, and session replay events" width="1512" height="982" data-path="images/user.png" />

## Your users

Each user shows their traits, when they were last active, and which [surfaces](https://interfere.com/~/*/surfaces) they've used. You populate this by identifying users from your app, which attaches a name and email to a session instead of an anonymous id. See Identity in your SDK guide ([Next.js](/sdk/next-js#identity), [Vite](/sdk/vite#identity)). Until you identify them, sessions stay anonymous.

## Session replays

Interfere records sessions so you can watch them back: the pages a user visited, the actions they took, and the problems they ran into along the way. From a problem, jump to the replays where it happened to see it in real context rather than from a stack trace alone.

Session replay is part of the SDK's capture and respects consent: it only runs when the `replay` category is allowed. Gate it from the Consent section on your [Next.js](/sdk/next-js#consent) or [Vite](/sdk/vite#consent) SDK page.
