> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/budgets-and-forecasts/owner-and-administrator/add-notes-to-workbook.md).
# Add notes to a workbook
Use workbook notes to give users instructions for completing the budget or forecast, details on how the budget model was built, or any other useful information.
{% hint style="info" %}
User permissions: Budgets & Forecasts and Manage Budgets & Forecasts
{% endhint %}
Notes can only be added by the budget owner. All users who have access to the workbook can [view the notes](/budgets-and-forecasts/contributor/edit-values-in-a-worksheet/open-workbook-notes.md).
1. Click the **Budget** menu and select **Open notes**.
2. In the **Notes** panel, click **Add Note**.
3. Write the note and format the text and/or add links using the text editor.
4. Add more notes on new tabs, if required (repeat steps 2 and 3).
5. Click **Close**.
You can take the following actions with a note in the **Notes** panel:
* To edit the note, click the tab of the note you want to edit, make your changes, then click **Close**.
* To rename a note tab, right-click the tab name and click **Rename**, change the name, then click **Close**.
* To delete a note, right-click the tab name and click **Delete** > **Yes**, then click **Close**.
---
# 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.phocassoftware.com/budgets-and-forecasts/owner-and-administrator/add-notes-to-workbook.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.
.png?alt=media)
