> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/advanced-features/drawpad-and-whiteboards/adding-a-whiteboard-or-blackboard-ifx.md).
# Adding a whiteboard IFX
## Adding a whiteboard from the IFX library
1. Open your menu or tablet, and then select **IFX** 
.
2. In the search field, enter "whiteboard" or "blackboard", and then select the magnifying glass icon.
3. Select one of the available IFX.
4. Move your mouse or right controller to position the IFX, and then left click or press the right trigger to place the IFX in the scene.
## Adding a whiteboard from your Drawpad
{% hint style="warning" %}
You can create a whiteboard only if you have permission to create IFX and your Drawpad is not connected to another whiteboard.
{% endhint %}
1. Open your Drawpad. See [Opening your Drawpad](/engage/advanced-features/drawpad-and-whiteboards/opening-your-drawpad.md) for instructions.
2. Select the **Whiteboard** tab.
3. On the **Whiteboard** tab, select **Create New**.
4. Move your mouse or right controller to position the whiteboard IFX, and then left click or press the right trigger to place the IFX in the scene.
---
# 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.engagevr.io/engage/advanced-features/drawpad-and-whiteboards/adding-a-whiteboard-or-blackboard-ifx.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.