> 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/pt/agente-realmjoin/client-menu.md).

# Interface de utilizador

Duas formas de os utilizadores interagirem com o RealmJoin no respetivo dispositivo: a clássica RealmJoin Tray e o Self-Service Portal baseado na Web.

O gerenciamento moderno de endpoints prospera quando os usuários têm autonomia para resolver suas próprias necessidades por meio de uma interface intuitiva e sem atritos.

Ao oferecer uma escolha clara entre o clássico **Bandeja do RealmJoin** e o abrangente **Portal de Autoatendimento**, garantimos que implantações de software e ferramentas do sistema estejam sempre a apenas um clique de distância.

A alta adoção depende dessa filosofia de "autoatendimento"; quando uma interface é ao mesmo tempo acessível e lógica, ela reduz a carga de trabalho da TI, minimiza o tempo de inatividade e transforma configurações complexas de back-end em uma experiência fluida e fácil de usar.

Esta seção da documentação apresenta as duas principais formas de os usuários interagirem com o ambiente RealmJoin.


---

# 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/pt/agente-realmjoin/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.