> For the complete documentation index, see [llms.txt](https://cc.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cc.docs.landis.cloud/setup/setup-wall-boards.md).

# Set Up Wall boards

Navigate to Configuration | Wallboards | Add.

Give the wall board a name and a description.  

Select one or multiple queues and/or IVRs specify the order displayed. 

Select desired data columns and the order displayed. See [Wallboards](/reports/wallboards.md) for column details.

Select an OU where the wall board should be located. See [Organizational Units](/administration/organizational-units.md)

Choose a picture for your wallboard (optional).

The following columns are supported for IVRs:

* Live
* Longest waiting
* Interactions
* Avg Handle
* Requested Callbacks

All columns are supported for queues.

{% hint style="info" %}
Wallboard are linked to an organization Unit. For a user to see a wallboard, they will need a data access policy assigned directly to the organization unit.
{% endhint %}

{% hint style="info" %}
The queue color shown on the wall board can be customized. Queues & IVRs | Select queue | Edit | Color
{% endhint %}


---

# 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://cc.docs.landis.cloud/setup/setup-wall-boards.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.