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

# Interface de utilizador

O gerenciamento moderno de endpoints prospera quando os usuários são capacitados a 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 as implantações de software e as ferramentas do sistema estejam sempre a apenas um clique de distância.

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

Esta seção da documentação apresenta as duas principais maneiras pelas quais os usuários podem interagir 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 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.realmjoin.com/pt/realmjoin-agent/client-menu.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.