> For the complete documentation index, see [llms.txt](https://docs.proliquid.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proliquid.xyz/settings/sound-alerts.md). # Sound alerts Manage all the sounds alerts in one place

Sound alerts settings for global mute, volume, and per-alert sounds.

Sound alerts control every audio notification in Proliquid. For the full list of alert types and where they appear, start with [Alerts](/features/alerts.md). ## Global controls Use global mute when you want visual notifications only. Use global volume to set the overall loudness for enabled sounds. Sounds are normalized so one alert type should not be unexpectedly louder than the others. ## Alert categories You can enable, disable, preview, and choose sounds for individual alert types:

Category	Examples
Terminal	Order fills and Terminal execution alerts.
Screener	Pump, dump, and volatility alerts from the Screener.
Feed alerts	Liquidation and whale alerts from market feeds.
News	Important news, website news, and social feed alerts.

Press play beside a sound to preview it before saving. ## When to customize Use distinct sounds when you want to identify alert type without looking at the screen. Mute noisy categories when you are monitoring a broad watchlist or when a market is repeatedly triggering low-quality alerts. --- # 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.proliquid.xyz/settings/sound-alerts.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.