<?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/762cfc7cab6b4df098ce2cdb7418a4c9&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/762cfc7cab6b4df098ce2cdb7418a4c9-64e068d293dd5dc0.gif</thumbnail_url><duration>592.32</duration><title>Uploading Customer IRLs for Quick Audit Readiness 🚀</title><description>Hey folks, in this video, I walk you through the process of uploading your customer&apos;s IRL into Beta to get them audit ready quickly, specifically for a SOC 2 audit. I cover the essential information needed for the upload, including a unique ID, request name, and request type, and how to handle different formats of IRLs. I also explain how to map the columns correctly and address common errors during the upload process. Please ensure you add the unique ID and request type before uploading, and remember that you can make changes after the upload is complete. Let’s get started on making this process as smooth as possible!</description></oembed>