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

# Desktop Client

The Windows app your team uses instead of the browser.

Hollow Peak ships with a native Windows client. It is the same workspace your team uses in a browser — tasks, projects, attendance, leave, documents, clients, enquiries, live chat, the store and communications — in an application that opens from the taskbar and keeps you signed in.

## What it is, and what it is not

The client reads your Hollow Peak site over HTTPS. It is not a second copy of your system and it holds no data of its own.

{% hint style="info" %}
**There is no database to configure.** The client never connects to MySQL. It talks to the API on your site, and every action is authorised on the server exactly as it would be in a browser. The only thing it needs to know is your site's web address.
{% endhint %}

That single fact shapes everything else on these pages:

* **Setup is an address, not a configuration file.** No credentials, no keys, no connection strings.
* **One installer serves every customer and every machine.** Nothing per-installation is baked into the build.
* **There is nothing in the files worth stealing.** Someone who copies the installed folder gets an application that asks for a server address and then asks them to sign in.

## Staying in step with your site

The client follows the server rather than carrying its own copy of your settings.

* **Feature modules.** Switch the store off on your site and Products and Orders disappear from the client's sidebar — immediately, without a restart, and without configuring the desktop separately.
* **Roles and permissions.** People see the sections their role allows. Hiding a link is a convenience only: every endpoint re-checks the same permission on the server, so a tampered-with client cannot reach anything its user could not already reach.
* **Theme.** The shared palette is published from the dashboard, and the client paints itself with it.

## Making it yours

Each machine can set the name shown beside the logo, the sidebar mark and the Windows taskbar icon, under **App Settings → This client**. The same screen can put you on Discord as working, if you want it.

## What is deliberately left in the browser

Site management stays on the web dashboard. The page builder, the site-wide media settings and the menu editor are canvas and file surfaces, and a partial version of them would be a way to damage a published page rather than a way to edit one.

Everything an employee does day to day is in the client.

## In this section

* [Installing the client](/docs/desktop-client/installing-the-client.md)
* [Rolling it out to your team](/docs/desktop-client/rolling-it-out-to-your-team.md)
* [Discord Rich Presence](/docs/desktop-client/discord-rich-presence.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hollow-peak.gitbook.io/docs/desktop-client.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.
