> 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/release-notes/terms-and-policies/product-release-communications.md).
# Product release communications
To stay updated with product updates, you can expect the following communications. This approach ensures you’re informed, prepared, and supported during and after product releases.
### Statuspage updates
*(1 week before the release)*
On the Fairmarkit Statuspage (), we post a high-level overview of the upcoming release one week before it is released. This provides you with insight into the release and gives you time to reach out and ask questions.
* Subscribe to emails: To ensure you don’t miss an update, subscribe to the statuspage email alerts.
### Release notes & documentation
(Day of the release)
On release day, [release notes](/release-notes/release-notes/buyers.md) are published to the documentation ([docs.fairmarkit.com](http://docs.fairmarkit.com/)), highlighting all changes in a release. Additionally, documentation is also available for more information about the features.
A banner linking to the release notes is displayed in the Fairmarkit application to ensure user visibility.
### Feature rollouts
We take a staged rolled-out approach for significant new features and control access with a configuration. This allows you to collaborate with your Fairmarkit team to learn about the feature changes in advance and determine the optimal timing for adoption.
### In-app onboarding
(With release, as needed)
For some new features, in-app onboarding tutorials will be added to guide users through functionality, enabling a seamless transition to the new experience.
### Monthly product emails
(Monthly after the release)
Once a month, you’ll receive an email with highlights of new feature releases for the month and a link to the release notes.
### Additional training
(After release, as needed)
Additional resources, such as webinars or click-through tutorials, may be included for larger releases to provide deeper insights and training.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.fairmarkit.com/release-notes/terms-and-policies/product-release-communications.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.