Opera Workspaces sync scope for workspace metadata and tab URLs across devices

Workspace sync behavior

Opera Workspaces provide visual tab grouping within a single browser window. When signed into an Opera account, the browser offers synchronization of open tabs, history, and settings across devices. The configuration surface does not specify whether workspace definitions — including workspace names, icons, and the assignment of tabs to workspaces — are included in the sync payload or remain local to each installation.

Unresolved constraint

Documentation and the Settings > Synchronization panel list generic categories such as "Open tabs" and "Settings" but do not enumerate workspace metadata as a distinct syncable item. This leaves the permission boundary ambiguous: a user who organizes tabs into workspaces on one device cannot predict whether that structure will appear on another signed-in device, or whether only the flat list of tab URLs will sync.

Goal: determine the exact sync scope for workspace metadata and tab-to-workspace assignments so that cross-device workflow expectations can be set accurately.

• Does the Opera account sync engine transmit workspace names, icons, and tab-group membership, or only the underlying tab URLs?
• If workspace metadata is synced, is there a configuration toggle to disable it independently of tab sync?
• When a workspace is created on a device that has never signed in, does the first sign-in merge or replace local workspace state?