> For the complete documentation index, see [llms.txt](https://help.brickspacelab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brickspacelab.com/slab/getting-started/global-settings/audio-settings.md).

# Audio

Audio settings in **Theme settings > Audio** control whether the theme may play interface sounds. When audio is enabled, you can add an **Audio picker** block so customers can choose their preference.

## How to change theme audio

{% stepper %}
{% step %}

#### Set the global toggle

* Open **Theme settings > Audio**.
* Turn **Enable audio interface sounds** on or off.
  {% endstep %}

{% step %}

#### Optional: customer control

* Add an **Audio picker** block where customers should toggle sound.
* Preview key actions (such as add to cart) with audio on and off.
  {% endstep %}
  {% endstepper %}

### Notes on audio

* When **Enable audio interface sounds** is off, storefront audio stays off.
* When it is on, the theme can use the preference from the **Audio picker** where that block is placed.
* Mobile browsers may still limit sound regardless of theme settings.

## Audio settings

| Setting                       | What it controls                                      |
| ----------------------------- | ----------------------------------------------------- |
| Enable audio interface sounds | Master toggle for theme interface audio. Default off. |


---

# 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://help.brickspacelab.com/slab/getting-started/global-settings/audio-settings.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.