> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/analytics+/working-with-analytics+/12.-adding-notes.md).

# 12. Adding notes

Analytics+ delivers an out-of-the-box and user-friendly annotation feature that allows you to add more perspective to your data. You can add different types of annotations with Analytics+:

* Canvas annotations capture priorities and perspectives for the entire report page.
* Data point annotations capture the context for a specific data point. In tables, cell-level notes enable adding data point annotations to record additional details for every cell.
* Row-level notes in tables allow you to add a notes column to include information applicable to the entire row.
* Footnotes in tables: IBCS recommends the display of footnotes in reports. You can present all the cell-level notes in a single footnote section.

{% hint style="info" %}
The annotation feature can be used only in chart and table mode.
{% endhint %}

[Learn more about adding notes for charts](/analytics+/working-with-analytics+/12.-adding-notes/notes-for-charts.md)

[Learn more about adding notes for tables](/analytics+/working-with-analytics+/12.-adding-notes/notes-for-tables.md)


---

# 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.inforiver.com/analytics+/working-with-analytics+/12.-adding-notes.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.