> For the complete documentation index, see [llms.txt](https://dexsport-3.gitbook.io/dexsport-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dexsport-3.gitbook.io/dexsport-docs/account/notifications.md). # Notifications The platform tells you when something happens on your account: a bet is placed, an event finishes, a bonus arrives, money moves in or out. Nothing has to be turned on for this, notifications come on their own. ## Where to find them Click the **bell icon** in the top right corner of the header. The panel opens with your notifications, newest first, each with the time it arrived. **Mark all as read** clears the unread state on all of them at once, and the cross closes the panel. ## What you get notified about * **A bet is placed.** The amount and the currency, with a pointer to your bet status in the profile. * **An event is over.** The notification names the event and carries a **View results** button that opens the [result page](/dexsport-docs/betting/event-results.md), where the score and the settlement of every market are shown. * **A bonus or free spins arrive.** The notification says what was credited and offers **View bonus**, which takes you to My Bonuses with the conditions. * **A deposit is credited.** It takes you to your transaction history in the profile. * **A withdrawal is processed.** Same place, the **Transactions** section with the amount, the token and network, the status and the transaction hash. The buttons inside a notification are the fastest route to the thing it is about. From the bet notification you land on your bet, from the event notification on the result page, from the bonus notification on My Bonuses. ## Settings The bell needs no setting up and always works. **Settings** controls something else, the mailings: * **Email.** Promotional material sent to your email address. * **Browser.** Notices about account actions delivered straight to the browser, even when the site is closed. These are different things: the bell shows what happens inside the platform, while those two switches govern email and browser delivery. More on the settings themselves in [Profile and settings](/dexsport-docs/account/profile-and-settings.md). ## If a notification did not arrive A notification is a convenience, not the source of truth. The record itself is always in your profile: bets in **My Bets**, deposits and withdrawals in **Transactions**, bonuses and free spins in **My Bonuses**. If a notification is missing but the operation went through, you will see it in those sections. --- # 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://dexsport-3.gitbook.io/dexsport-docs/account/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.