> For the complete documentation index, see [llms.txt](https://docs.zeedrive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zeedrive.com/administration-guide.md).

# Administration Guide

A <code class="expression">space.vars.PRODUCT\_NAME</code> subscription administrator is responsible for all administration activities ranging from setting up users and network drives through to deploying the <code class="expression">space.vars.PRODUCT\_NAME</code> client and updating it.

Administration is performed through the <code class="expression">space.vars.PRODUCT\_NAME</code> *Administration Console*.

<figure><img src="https://4182749601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBkDVFDwNmEHlZv1KwwiY%2Fuploads%2FfonfKLTMtihJZQ949kKM%2Fimage.png?alt=media&amp;token=bf46cb7f-5f28-4b66-9075-1e95c52500b7" alt=""><figcaption><p>The administration functions available from the action button on the Administration Console</p></figcaption></figure>

The Administration Console is a Windows app that runs on your computer, its not a web portal. It sits in your system tray so it doesn't clutter your desktop until you need to use it. The Administration Console will start-up automatically when you sign in to Windows, so its always available to you.


---

# 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.zeedrive.com/administration-guide.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.
