> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/realmjoin-agent/client-menu.md).

# User Interface

Two ways users interact with RealmJoin on their device: the classic RealmJoin Tray and the web-based Self-Service Portal.

Modern endpoint management thrives when users are empowered to solve their own needs through a frictionless, intuitive interface.

By providing a clear choice between the classic **RealmJoin Tray** and the comprehensive **Self-Service Portal**, we ensure that software deployments and system tools are always just a click away.

High adoption relies on this "self-service" philosophy; when a UI is both accessible and logical, it reduces IT overhead, minimizes downtime, and transforms complex backend configurations into a seamless, user-friendly experience.

This documentation section introduces the two primary ways users can interact with the RealmJoin environment.


---

# 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.realmjoin.com/realmjoin-agent/client-menu.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.