<?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/410e4a12383c4e5a91bab4a3fce86d95&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/410e4a12383c4e5a91bab4a3fce86d95-374db57cf5c07271.gif</thumbnail_url><duration>299.008</duration><title>Orah x Veracross Integration - Objects we pull from Veracross</title><description>In this video, I walk you through the Veracross integration setup, highlighting the various objects we sync from Veracross to ORA, including student data, contact information, staff, groups, schedules, locations, and reason codes. I explain that while most objects sync automatically every 24 hours, you have the option to manually force a sync whenever needed, especially after making changes. It&apos;s crucial to customize settings based on your school&apos;s requirements, particularly for approved contacts who can report absences without an ORA account. I encourage you to familiarize yourself with these features and utilize the manual sync option as necessary to ensure accurate data flow.</description></oembed>