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

# Using

Learn how to use Lenses

This space covers setup, deployment, and configuration.

The Lenses User Guide now lives in a separate space.

Use it for day-to-day product usage, including:

* navigating the UI
* exploring environments and resources
* working with topics, schemas, and connectors

<a href="https://docs.lenses.io/latest/user-guide" class="button primary">Open the User Guide</a>

### Where to start

Use this docs space when you need to:

* install Lenses
* connect Lenses to your Kafka environment
* configure HQ or Agent

Use the User Guide when you need to:

* learn how the interface works
* explore data and services
* understand day-to-day workflows

### Suggested path

If you are new to Lenses:

1. Start with [Setting Up Community Edition](/latest/devx/6.2/getting-started/quickstart.md)
2. Follow the [Hands-On Walk Through of Community Edition](/latest/devx/6.2/getting-started/quickstart/hands-on-walk-through-of-community-edition.md)
3. Continue in the [Lenses User Guide](https://docs.lenses.io/latest/user-guide)


---

# 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.lenses.io/latest/devx/6.2/getting-started/using.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.