<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/66c4786d5c9a4ee0929c4630606c5bc6&quot; frameborder=&quot;0&quot; width=&quot;1800&quot; height=&quot;1350&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1350</height><width>1800</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1350</thumbnail_height><thumbnail_width>1800</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/66c4786d5c9a4ee0929c4630606c5bc6-fb11e42c91831391.gif</thumbnail_url><duration>214.784</duration><title>Uni-and Bi-directional Auto-sync between SSC Cloud Spaces</title><description>This Loom explains how to enable and test AuthSync, then make synchronization bidirectional between Confluence spaces. It shows configuring AuthSync in space settings via Sync Space List, selecting the target space, enabling AuthSync, and submitting, then verifies changes by editing a Qt Release Notes page and confirming the update appears in the support hub. It then demonstrates enabling auto-sync on the destination space to allow edits from support to propagate back to the product hub, such as removing an item and seeing it reflected. The Loom cautions that if both sides edit the same page before a sync runs, there is no merge and the last sync wins due to a Confluence limitation.</description></oembed>