> For the complete documentation index, see [llms.txt](https://docs.fairmarkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmarkit.com/buyers/events/collaboration-tools/internal-notes.md).

# Internal notes

With Internal Notes, you can enter notes about an event and add attachments and then share them with your team. These notes are for internal use only and will not be shared with suppliers. This is helpful for compliance purposes to track information shared outside of Fairmarkit, such as through phone calls or meetings.

{% hint style="info" %} <mark style="color:purple;">**Note**</mark><mark style="color:purple;">: Depending on your integration, internal notes may be sent back to your purchasing application.</mark>
{% endhint %}

<figure><img src="https://docs.fairmarkit.com/content/buyers/images/internal-notes_thumb_0_0.png" alt=""><figcaption></figcaption></figure>

### Open internal notes <a href="#openinternalnotes" id="openinternalnotes"></a>

Note: From a draft event, click the Internal Notes button to add notes to the event.

1. Open an event.
2. Select **actions > Add note/View notes**.\
   The Internal Notes dialog box displays.

### Add an internal note <a href="#addaninternalnote" id="addaninternalnote"></a>

1. In **Add note**, enter your note. Click the **attach** :paperclip: button to select and attach a file to the note.
2. Click the **Add Note** button.\
   The note is added, and an indicator will display on the Comments button.

### View internal notes history <a href="#viewinternalnoteshistory" id="viewinternalnoteshistory"></a>

From Internal Notes, you can view a history of past notes you've saved for the event. Each note is date and time-stamped with the user.


---

# 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.fairmarkit.com/buyers/events/collaboration-tools/internal-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.
