{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/b7d0fd33ebdd47afbfa511fbed555cb4\" frameborder=\"0\" width=\"1800\" height=\"1350\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1350,"width":1800,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1350,"thumbnail_width":1800,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/b7d0fd33ebdd47afbfa511fbed555cb4-826828eb4b19d500.gif","duration":348.8,"title":" Restricting External Sync with Whitelisting to Enhance Security","description":"This Loom explains how to push updates to a partner via cloud to cloud sync without allowing unsolicited inbound syncing. It emphasizes checking that managed or automatic whitelisting (write access) is off so only an outbound push door is exposed, while incoming requests are still able to be made. The video demonstrates creating a sync to Totoro, sending a token by email, importing it in the Partner Hub, and seeing that the partner can view the space but cannot push until access is approved. If the partner needs bidirectional syncing, they submit a Request Sync from Space Settings to the source admin, who then approves to enable two way syncing."}