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

# Dashboard

<figure><img src="https://1678833186-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYKOCz2PA9ulNwL0J4JUq%2Fuploads%2Fve0cNyhD58diUPOpWSA6%2FFeature%20Section%202.png?alt=media&amp;token=22ed7232-fd7b-4c33-a8ad-2cc37b8effb7" alt=""><figcaption></figcaption></figure>

After creating your account, the **CloudFilt Dashboard** is the first place you will interact with.\
It serves as your **control center**, giving you direct access to all available features and a clear overview of your websites’ status.

#### What you can do in the Dashboard :

* **Add and configure websites** in just a few steps.
* **Check service status** to see whether CDN, WAF, or other protections are active.
* **Manage DNS settings and integrations** without switching between multiple tools.
* **Monitor traffic and security activity** through real-time logs and analytics.
* **Access documentation and resources** directly from the interface.

The Dashboard is designed to be **simple yet powerful**, so you can focus on securing and optimizing your websites without complexity.


---

# 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.cloudfilt.com/getting-started/quickstart.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.