# Users and sessions

Connect captured failures with the people and journeys they affected.


![Platform demonstration: Inspect sessions connected to a problem.](/docs/screenshots/sessions-light.webp)

## Identify your application user

```ts title="After sign-in"
import { identify } from '@everock/sdk';
identify({ id: 'customer_123' });
// On sign-out:
identify(null);
```

Use a stable non-sensitive identifier. The browser SDK also maintains a tab-scoped session ID and, when storage is available, a device identifier. These are different concepts; several sessions can belong to the same user.

## User details

The Users view and incident impact panels derive counts and trends from captured evidence. Affected users are not equivalent to all registered accounts in your own database. A user with no received telemetry may not appear.

## Sessions and replay

Open a session to inspect its observed timeline and associated failures. A playable replay exists only when replay was enabled locally and remotely, consent and sampling allowed it, chunks arrived, and storage/retention permits access.

DOM replay is not a video capture of the device or a native mobile recorder. Browser and operating-system metadata are detected context, not an installed native SDK.

See [browser capture](/docs/sdks/browser), [replay](/docs/features/session-replay), and [privacy](/docs/features/privacy).