> For the complete documentation index, see [llms.txt](https://docs.servoy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.servoy.com/guides/deploy/server-configuration/client-sessions.md). # Client Sessions The Clients node on the Servoy Admin page provides an overview of all connected clients, grouped by the solution they are running. When the Servoy Application Server is part of a Servoy Cluster, the Clients overview will also show all client connected to the other Servoy Application Servers within the cluster. The link at the top allows to toggle the grouping between Solution/Server to Server/Solution. The clients overview provides functionality to: * Send a message to clients * Close clients * Flush the data cache of all clients The first two of these actions can be done on a specific client, on all clients using a certain solution, on all clients connected to a certain Servoy Application Server within a Servoy Cluster or to all clients. By clicking the client link, all details of the specific client can be viewed. --- # 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.servoy.com/guides/deploy/server-configuration/client-sessions.md?ask=&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.