{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/410e4a12383c4e5a91bab4a3fce86d95\" frameborder=\"0\" width=\"1280\" height=\"960\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":960,"width":1280,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":960,"thumbnail_width":1280,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/410e4a12383c4e5a91bab4a3fce86d95-374db57cf5c07271.gif","duration":299.008,"title":"Orah x Veracross Integration - Objects we pull from Veracross","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's crucial to customize settings based on your school'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."}