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

# Using the Console

**Green Stack Console** is a unified, web-based application where you configure and manage buildings connected to Green Stack using a computer, laptop, phone, or tablet.&#x20;

The console URL is <https://greenstack.app>

### Compatible Browsers

We recommend that you use the most up-to-date browser that's compatible with your operating system or device. The latest version of the following browsers (mobile and desktop) are officially supported:

* Microsoft Edge
* macOS Safari
* Google Chrome
* Mozilla Firefox

{% hint style="info" %} <mark style="color:blue;">**Please Note**</mark>

* *The console is only available via HTTP/S*
* *JavaScript must be enabled in your browser*
* *The console is not compatible with* [*Internet Explorer*](https://blogs.windows.com/windowsexperience/2022/06/15/internet-explorer-11-has-retired-and-is-officially-out-of-support-what-you-need-to-know/)
  {% endhint %}

## Basic Console Layout

<figure><img src="https://2648111699-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LgFaENsKBt4Y2w8b20l%2Fuploads%2F3xU3yiaWJglZbZlpphTa%2Fschematic--shell-root.png?alt=media&amp;token=17703b28-0d41-4957-a919-bbe23244f168" alt=""><figcaption></figcaption></figure>

The console consists of three basic elements:

#### Application Shell

The shell contains the global application header and main navigation. These elements are always visible. The primary view content is displayed in the content area.

#### Global Header

As the name implies, the header is a static UI element available at all times. The header contains the ***Green Stack logo***, the current **module path**, **action buttons** for searching, commanding, and getting help, and the **user account menu**.

## Keyboard Shortcuts

{% tabs %}
{% tab title="Global Shortcuts" %}

<table><thead><tr><th width="229">Combination</th><th>Description</th></tr></thead><tbody><tr><td><strong><code>F1</code></strong>, <strong><code>Ctrl</code></strong> + <strong><code>?</code></strong></td><td>Open Help Panel</td></tr><tr><td><strong><code>Ctrl</code></strong> + <strong><code>/</code></strong></td><td>Open Command Prompt</td></tr><tr><td></td><td></td></tr><tr><td><strong><code>F1</code></strong>, <strong><code>Ctrl</code></strong> + <strong><code>?</code></strong></td><td>Switch User</td></tr><tr><td><strong><code>Ctrl</code></strong> + <strong><code>,</code></strong></td><td>System Preferences</td></tr></tbody></table>
{% endtab %}

{% tab title="Engineering" %}

<table><thead><tr><th width="229">Combination</th><th>Description</th></tr></thead><tbody><tr><td><strong><code>Ctrl</code></strong> + <strong><code>E</code></strong></td><td>Edit Current Record</td></tr><tr><td><strong><code>Ctrl</code></strong> + <strong><code>S</code></strong></td><td>Save Current Record</td></tr><tr><td><strong><code>Ctrl</code></strong> + <strong><code>D</code></strong></td><td>Duplicate Current Record</td></tr><tr><td><strong><code>Esc</code></strong></td><td>Cancel Current Editing Session</td></tr></tbody></table>
{% endtab %}
{% endtabs %}


---

# 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.greenstack.dev/fundamentals/using-the-console.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.
