> For the complete documentation index, see [llms.txt](https://docs.omnileads.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnileads.net/english/wallboard-for-business-pro/creating-a-wallboard.md).
# Creating a Wallboard
To create a Wallboard, you must access the Main Menu -> Wallboard, and click on the Create button:
There we will need to configure the following fields:
Name: the name we will give to our Wallboard
Description: a brief description.
Duration: the duration that the pages will have in case of creating multiple views on the same "wall".
Is-Public?: will allow us to share this wallboard with other supervisor users and/or administrators of the platform.
By clicking on Save, we will be able to view the real-time Wallboard created and ready for configuration:
The different view icons will allow us to: delete, edit, add widgets/pages, and open the wallboard in a new tab for viewing.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.omnileads.net/english/wallboard-for-business-pro/creating-a-wallboard.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.