<?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/c79fa9f45f1142bf8d20fd3b74193678&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/c79fa9f45f1142bf8d20fd3b74193678-c4dccbabf8ebd872.gif</thumbnail_url><duration>664.448</duration><title>How Group Trip Sync Updates Subtrips</title><description>This Loom explains the latest group syncing behavior for keeping subtrips aligned with a main group itinerary. When a subtrip is created, it copies the core itinerary details and synced elements like media and documents, but booking and pricing is fully unlocked at the subtrip level and later pricing updates from the group do not sync. Subtrip activity titles and room selections become managed locally after subtrip edits or selections, and room inventory added after subtrip creation will connect. New items added to the group push to subtrips while deleted items are removed, and syncing can show errors when group itinerary changes fall outside subtrip dates. It also covers opting into an existing trip and notes that activities copy but dates do not, with outside-date activities skipped and potential doubles if activities were manually added.</description></oembed>