> For the complete documentation index, see [llms.txt](https://docs.spreo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spreo.io/dashboard/boards.md).
# Boards
Sort, move and clone the boards in your team dashboard.
By default, your boards are shown in descending order from the last time they were visited.
You can change this by adjusting the filter on the top right of your boards view.
Any board that is not assigned to a folder will appear in your dashboard 'root'. If you move a board to a folder it will no longer be visible at the root level but you can search for it.
To move a board into a folder, or to another team, open the board's 3-dot menu and choose 'Move'.
To move a board out of a folder, use 'Move' again and choose the top level of the team. The 'Back To Root' link takes you back to the top level of your team's boards.
### Cloning a board
You can make a clone of any board in your dashboard. Use the 3-dot menu to access the options and select 'clone'. This will allow you to name the cloned board and set its location.
* Cloning a board copies everything on the board.
* You can clone a board across teams and folders.
* If there was an active meeting on the board you cloned, you will become the Host on the new board.
---
# 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.spreo.io/dashboard/boards.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.
