Configure user settings storage for WebAgent

Introduced in DC2025.01

WebAgent can store supported user preferences in a central SQL database. Saved preferences can follow the same user when they sign in from another browser or device connected to the same WebAgentService and settings database. Central storage does not cover every display or audio preference.

Which preferences use central storage?

The following preferences use central storage when the capability is enabled. Available controls depend on your version, layout, and enabled features.

  • Personal contact groups, group membership, and expanded or collapsed group state.
  • Waiting and Connected queue grouping, sorting, and compact or extended dialogue view.
  • Keyboard shortcuts enabled or disabled, and auto-answer enabled or disabled.
  • Selected , saved sidebar tab selection and expanded or collapsed view, and last navigation destination.
  • Notification time, first open dialogue tab, incoming text-conversation ringtone, and incoming text-message alert.
  • Previously selected transfer tab, agent overview panel state, conversation-widget configuration, and active UI plugin.
  • Computer telephony integration (CTI) preferences: search after accept; pop-up behavior for a single match, multiple matches, or no match; no-match entity; single-match page; click-to-dial action; pop on session switch; wildcard search; and notifications.

Browser-specific settings and exceptions

  • Theme: handled separately from the user-settings database. Do not use a theme change to check central storage.
  • Browser-only display details: hiding inactive queue items, customized panel width, and collapsed information are saved in browser storage, not this database.
  • Sidebar exception: selecting a tab can be stored centrally, but deselecting the tab to return to the overview can save that tab choice only in the current browser.

Note

Do not assume that the audio-call ringtone or auto-answer delay follows the user. The reviewed settings controls save these values in browser storage, even though auto-answer enabled or disabled uses central storage. Confirm behavior for your deployed version with Support before relying on these values across devices.

Existing browser preferences

Enabling central storage does not upload all existing browser preferences. A preference may still appear in the original browser because it reads a local value; this does not mean it has been saved centrally. After central storage is enabled, select and save the supported preferences you need, then verify them in another browser.

Personal contact groups and memberships have a separate import path. When the corresponding server value is absent, loading contacts can import that data from the current browser's existing contact-group storage (IndexedDB). This is not a merge of contact lists from every browser, and existing server values take precedence. Use the browser containing the required groups and memberships, then verify them elsewhere before clearing its browser data.

Database schema creation or migration is separate from importing browser preferences. Do not assume changes appear immediately in other sessions that are already open.

Validate central storage

  1. Sign in with a test user after central storage is enabled.
  2. Change Notification time to a different available value, and record that value.
  3. Sign out, then sign in as the same user from another supported browser or device using the same WebAgentService and settings database.
  4. Open Settings and confirm that Notification time matches the value you selected.
  5. If it does not match, ask your administrator to check the central-storage capability, database connection, and user-settings record. Do not use a theme change as a substitute for this check.

Configure central storage

, by:

  • manually activating the capability by adding a setting in one or more UCC SharePoint sites.