> For the complete documentation index, see [llms.txt](https://help.cloudstoragesec.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cloudstoragesec.com/console-overview.md).
# Console Overview
In the How to Configure section, we covered our first bucket activation to enable scanning and our first data classification schedule. Now let's take a closer look at the rest of the console.
The following sections will walk you through each area of the console and what you can expect from it. The goal, in general, has been to make the scanning, classifying, and protection of your objects simple and straight forward. The console is simple to get around with left side and top navigation. The left side will take you between the main Dashboard view, Bucket Protection and/or Schedules page, the Configuration options and the User Management area. While the top allows for in-place upgrades, your account management options, and Group switching.
Console dashboard page
---
# 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://help.cloudstoragesec.com/console-overview.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.
