> 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/suppliers/suppliers/getting-started/how-do-i-stay-updated-on-my-events/notifications.md).
# Notifications
When working on events, you can add comments to ask questions and communicate with the event's buyer about the event. You'll receive a notification when you receive a message, or a comment is added to an event.
### View notifications
On the Fairmarkit menu, click **Notifications**. You can preview the comment or message. Click the notification to view the message or open the comment in the event. Once clicked, the notification is removed.
### Subscribe / Unsubscribe from notifications for an event
To toggle on or off emails and notifications for the event comments, open the event and then click the **Subscribe** / **Unsubscribe from notifications**  button in the Comments area.
### Change notification settings
From the [Notifications settings](/suppliers/suppliers/getting-started/how-do-i-stay-updated-on-my-events/notification-settings.md) screen, you can control if you want to receive emails for comments.
* From the Fairmarkit menu, click *your name* and select **Notification Settings**.
---
# 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/suppliers/suppliers/getting-started/how-do-i-stay-updated-on-my-events/notifications.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.
