> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/platform-user-guide-book/user-registration-and-account-confirmation/cockpit-menu.md). # Cockpit Menu

The **Cockpit Menu** serves as the central hub for accessing all functional pages of the platform, including Devices, Groups, Alarms, Templates, Administration, and FOTA\* . This section is designed to support the organizational aspects of the platform, providing users with tools for device and group management, alarm configurations, and administrative actions. Unlike other sections, the Cockpit Menu emphasizes operational tasks, featuring elements such as Groups, the Home button, and Quick Access Dashboards, making it a streamlined and action-oriented interface for day-to-day operations. {% hint style="warning" %} \*FOTA ( Firmware update Over The Air ) is not available on all tenants and is enabled on request. {% endhint %} --- # 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.g-iot.io/platform-user-guide-book/user-registration-and-account-confirmation/cockpit-menu.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.