> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/use/handle-conversations/webagent/set-webagent-preferences.md). # Set WebAgent preferences Adjust WebAgent display, notification, shortcut, and text-alert preferences. In the new layout, select **Settings** (the gear icon) in the left navigation. In the classic layout, open the profile menu (**MePerson**) in the upper-right corner and select **Settings**. Available choices can depend on your environment. ## General settings * **Theme:** Choose an available light, dark, or Teams appearance. * **Notification time:** Choose how long notifications remain visible, including **No Timer** where offered. * **First open dialogue tab:** Choose the tab displayed when a new dialogue opens. If that tab is unavailable for the dialogue, WebAgent shows **Conversation** instead. * **Enable shortcuts:** Turn WebAgent shortcuts on or off. See [Use keyboard shortcuts](/use/handle-conversations/webagent/use-keyboard-shortcuts.md) for common actions. ## Audio alerts for text conversations Under **Audio settings**, choose a ringtone for an incoming text conversation or an alert for a new text message, or set either to **None**. These preferences apply to text channels such as email, WebChat, WhatsApp, and SMS, not voice-call audio. Your browser may block alert sounds until you interact with the WebAgent page. If a configured alert does not play, click or otherwise interact with the page first. When your administrator enables central storage, notification time, the first open dialogue tab, shortcuts, and text-conversation audio alerts can follow you to another browser or device using the same WebAgentService and settings database. Theme is not stored by the user-settings database. See [Configure WebAgent user settings storage](https://github.com/AnywhereNow/atlas-docs/tree/main/channels-integrations/webagent/configure-webagent-user-settings-storage/README.md) for coverage and browser-migration guidance. Without central storage, clearing browser data or changing browsers or devices can reset locally stored preferences. --- # 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://atlas.anywhere.now/use/handle-conversations/webagent/set-webagent-preferences.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.