> 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.

<figure><img src="https://content.gitbook.com/content/FCveeKRMBLpu9Vhum7Zb/blobs/bYudClv0bFOPW9nCEqvI/product-comm_thumb_0_0.png" alt=""><figcaption></figcaption></figure>

### Statuspage updates <a href="#statuspageupdates" id="statuspageupdates"></a>

*(1 week before the release)*

On the Fairmarkit Statuspage (<https://fairmarkit.statuspage.io/>), 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.

<figure><img src="https://content.gitbook.com/content/FCveeKRMBLpu9Vhum7Zb/blobs/rKVCGbjRTiR9emQ0WrEn/statuspage_thumb_0_0.png" alt=""><figcaption></figcaption></figure>

* Subscribe to emails: To ensure you don’t miss an update, subscribe to the statuspage email alerts.

<br>

### Release notes & documentation <a href="#releasenotesdocumentation" id="releasenotesdocumentation"></a>

(Day of the release)

On release day, [release notes](https://docs.fairmarkit.com/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.

<figure><img src="https://content.gitbook.com/content/FCveeKRMBLpu9Vhum7Zb/blobs/RPH7y6e5vwQKXOBKQyH6/release-notes_thumb_0_0.png" alt=""><figcaption></figcaption></figure>

A banner linking to the release notes is displayed in the Fairmarkit application to ensure user visibility.

<figure><img src="https://content.gitbook.com/content/FCveeKRMBLpu9Vhum7Zb/blobs/ZRwGPyD9PQ3I8zKpv2oU/banners_thumb_0_0.png" alt=""><figcaption></figcaption></figure>

### Feature rollouts <a href="#featurerollouts" id="featurerollouts"></a>

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.

<figure><img src="https://content.gitbook.com/content/FCveeKRMBLpu9Vhum7Zb/blobs/PgBTzm5Nirz4RTN3vDMe/configs_thumb_0_0.png" alt=""><figcaption></figcaption></figure>

### In-app onboarding <a href="#inapponboarding" id="inapponboarding"></a>

(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.

<figure><img src="https://content.gitbook.com/content/FCveeKRMBLpu9Vhum7Zb/blobs/5SOb5FPA9h4EAPon4M2G/onboarding_thumb_0_0.png" alt=""><figcaption></figcaption></figure>

### Monthly product emails <a href="#monthlyproductemails" id="monthlyproductemails"></a>

(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.

<figure><img src="https://content.gitbook.com/content/FCveeKRMBLpu9Vhum7Zb/blobs/MGjiyrgR4Xok74Jy0qvd/monthly-email_thumb_0_0.png" alt=""><figcaption></figcaption></figure>

### Additional training <a href="#additionaltraining" id="additionaltraining"></a>

(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.

<br>


---

# 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/release-notes/terms-and-policies/product-release-communications.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.
