> For the complete documentation index, see [llms.txt](https://support.hivo.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.hivo.co/dashboard.md). # Dashboard When you login to your HIVO account, you will be taken to the HIVO Dashboard. The Dashboard in HIVO is a customizable interface made up of **multiple configurable sections**, providing users with quick and intuitive access to key information. Admins can adjust the components of the Dashboard to suit specific management, monitoring, and navigation needs within the system. HIVO offers **two dashboard formats** for users to select and customize their working interface: * **Default Dashboard** This is the default interface displayed when users are not assigned to any customized dashboard. It provides basic components for quick access to key system features.

Default Dashboard

* **Custom Dashboard** This is a personalized dashboard **configured by Admins** to suit the specific needs of individual users or user groups.
### How to Access and Configure Dashboards **Admin users can access and configure dashboards** in one of the following ways: * Go to **Client Profile** → **Settings** → **Dashboard Settings or** * Go to **Profile** → **Dashboard Settings** 👉 From here, admin can: * Define display content for specific users or user groups. * Customize layout, background images, logos, and other interface elements. * Assign appropriate dashboards to individual users or groups.

Dashboard Settings

#### 👉 Read more about [**customizing your Dashboard**](https://support.hivo.co/client-profile/client-profile-settings/dashboard-settings) here. By customizing and organizing the components of the Dashboard, users can benefit from a personalized workspace that enhances efficiency and clarity in digital asset management. --- # 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://support.hivo.co/dashboard.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.