> For the complete documentation index, see [llms.txt](https://docs.lootlocker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lootlocker.com/players/multi-user/how-to/multi-user-in-a-server-context.md).

# In a Server Context

In a server context, managing multiple users is different from a client game. The server typically [impersonates players or exchanges tokens](/server/unreal-server/how-to/unreal-server-impersonation.md) to obtain a Game API session token for each player, then uses the SDK to manage multi user state and make requests for many users in a secure context.

### How it Works

* The server obtains a session token for each player (using impersonation or token exchange).
* The SDK's `StartSessionManual` method is used to add each session to the multi user state.
* You can then make API calls for any player by specifying their ULID.
* Remember to use all the techniques from our guide on [how to end sessions and manage state](/players/multi-user/how-to/end-sessions-and-manage-state.md) so that you have the correct sessions active and ready in your server context.

For implementation details, refer to our [impersonation how to](/server/unreal-server/how-to/unreal-server-impersonation.md)


---

# 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.lootlocker.com/players/multi-user/how-to/multi-user-in-a-server-context.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.