> For the complete documentation index, see [llms.txt](https://docs.fenixpyre.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/whats-new-notifications.md).

# What's New notifications

Stay on top of FenixPyre Cloud updates without leaving the Admin Dashboard.

A **What's New** bell in the header (top-right, near Help & Feedback and Docs) shows when there are unread Cloud release notes. Open it to skim the latest features and improvements, then jump to the full [What's New](https://docs.fenixpyre.com/release-notes/fenixpyre-cloud-releases/whats-new.md) page when you want more detail.

{% hint style="info" %}
**Rolling out gradually.** The What's New bell is controlled by a feature flag and may not be visible in every organization yet. If you do not see it, you can still read updates on the [What's New](https://docs.fenixpyre.com/release-notes/fenixpyre-cloud-releases/whats-new.md) docs page.
{% endhint %}

## What you see

| Element      | What it means                                                                                                                       |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
| Bell icon    | Opens the What's New popover. *(UI label: confirm `aria-label` / tooltip — expected **What's new**.)*                               |
| Unread dot   | Newer releases than the ones you last opened.                                                                                       |
| Popover list | Release items with title, short bullets, date, and category (New Feature, Improvement, or other).                                   |
| **View all** | Opens the full [What's New](https://docs.fenixpyre.com/release-notes/fenixpyre-cloud-releases/whats-new.md) docs page in a new tab. |
| Empty state  | **No updates right now** when there is nothing to show, or if the feed cannot be loaded.                                            |

## How unread state works

1. When you open the dashboard, the header loads the latest release notes once.
2. If the newest release date is newer than what you last opened, the bell shows a dot.
3. Opening the popover clears the dot for that browser. The seen date is stored in the browser (`whats_new_seen`) and is **not** cleared when you log out.
4. The next time a newer release is published, the dot appears again.

## Tips

* Release notes in the popover match the public What's New docs — the same content for every organization.
* If the feed fails to load, the popover shows the empty state and still offers **View all** so you can open the docs.
* The older third-party changelog launcher in the corner of the dashboard has been removed; use the What's New bell (or the docs page) instead.


---

# 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.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/whats-new-notifications.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.
