> 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/installing-the-client.md).

# Installing the client

From the installer to a signed-in workspace.

The installer is a single `HollowPeak-Setup.exe`. It is self-contained: .NET and the Windows App SDK travel inside it, so there is nothing to install first.

## Requirements

* Windows 10 version 1809 (build 17763) or newer, 64-bit
* Network access to your Hollow Peak site

No administrator rights are needed. Setup installs for the person running it, into their own `%LOCALAPPDATA%\Programs\Hollow Peak`, so there is no UAC prompt.

## Running setup

1. Run `HollowPeak-Setup.exe`.
2. Choose whether you want a desktop shortcut, and whether the client should start when Windows does.
3. **Enter your site address** when asked — the same address you use in a browser, such as `example.com`. Setup works out the rest.
4. Finish, and open the client.

The address step is optional. Leave it blank and the client asks the first time it opens, which is often the easier choice when someone else will be using the machine.

{% hint style="success" %}
Whatever you type is tidied up for you. `example.com`, `https://example.com` and `https://example.com/dashboard` all mean the same server, and all three are accepted.
{% endhint %}

## First run

If no address was given during setup, the client opens on a short setup screen and asks for one. It then checks the address before keeping it, so a typo is caught there and then rather than turning into a sign-in screen that can never succeed.

After that, sign in with your own Hollow Peak email address and password — the same account you use on the website.

## Signing in for the first time, on a brand-new installation

The client cannot create accounts; it signs in to accounts that already exist on your site. So the order is always:

1. Install Hollow Peak on your server and complete its setup, which creates the owner account.
2. Sign in to the website once as the owner.
3. Install the desktop client and sign in with that same account.

For colleagues, add them under **People** on the dashboard first. They can then install the client and sign in immediately.

## Changing the server later

**App Settings → Connection → Change server.** This signs you out and returns to the setup screen. Both go together on purpose: a sign-in token is only meaningful to the server that issued it.

## Where settings are kept

In `%LOCALAPPDATA%\HollowPeak`:

| File            | What it holds                                    |
| --------------- | ------------------------------------------------ |
| `server.json`   | The site address                                 |
| `session.bin`   | Your sign-in token, encrypted with Windows DPAPI |
| `branding.json` | This machine's name, logo and icon choices       |

`session.bin` is encrypted so that only the same Windows user on the same machine can read it. Uninstalling leaves this folder alone, so reinstalling does not make anyone set the client up again. To sign a machine out completely, delete `session.bin`.


---

# 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/installing-the-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.
