> For the complete documentation index, see [llms.txt](https://docs.tezos-homebase.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tezos-homebase.io/dao-explorer-proposals-and-voting/home-page.md).

# Home Page

This page is where you can see a snapshot of your DAO's governance token, voting addresses, and active proposals.

**View configuration** - this shows you the voting settings of your DAO, for reference. If you need a refresher on what all those terms mean, see the FAQ on  ["How to configure your DAO in Homebase"](/how-to-configure-your-dao-in-homebase.md)

TO WRITE: The cycles section is important to understand, because in Tezos, (explanation of why you have to wait to start your first vote, when you can vote etc)

**Current Cycle** - 

**Time Left in Cycle** - 

**Tokens Locked -** 

**Voting Addresses** - the number of addresses who have voting power in this DAO

**Active Proposals** - the number of active proposals that can be voted on

Top Addresses Section:

**Available Staked** - 

**Total Staked** - 


---

# 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.tezos-homebase.io/dao-explorer-proposals-and-voting/home-page.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.