> 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/sticky-notes/creating-a-sticky-note-from-the-wrist-control.md).

# Creating a sticky note from the wrist control

1. Raise and rotate your left hand as if to look at a wrist watch.
2. Use your right controller to tap the sticky note icon.
3. A keyboard and sticky note appear. Use the keyboard to enter the text that you want to appear on your sticky note, and then select the tick icon on the sticky note.

![Creating a sticky note from the wrist menu](https://3460182399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwVx6bvwqEE7tD0TYOcfj%2Fuploads%2Fgit-blob-23cc1002d9e899473242dcaab43f5bbb57ab513e%2Fsticky_note_from_wrist.jpg?alt=media)

4\. Move your controller to position the sticky note, move the thumbstick left and right to adjust the scale, and move the thumbstick up and down to adjust the distance from you. Press the trigger to place the sticky note.

{% hint style="info" %}
If you move the sticky note close to the surface of an interactive board, such as a whiteboard or blackboard, the sticky note snaps to the surface of the board.
{% 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://docs.engagevr.io/engage/advanced-features/sticky-notes/creating-a-sticky-note-from-the-wrist-control.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.