<?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/f2a1125ade3f46f38c8689b123645eda&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/f2a1125ade3f46f38c8689b123645eda-998ca5895b2ed0ce.gif</thumbnail_url><duration>165.145</duration><title>Setting up an admin internal workflow</title><description>This Loom explains the Admin Internal Workflow setting in Options Advanced under Workflow Templates. When Admin Internal Workflow is toggled to yes, residents are unable to make submissions and the form is hidden from the resident portal, negating the target audience setting that would otherwise show it to everyone. After saving the form as an internal admin workflow, it disappears from the Resident Portal Request page but remains available in the Admin Portal under New Request to admin staff, including options to assign it to residents or admins while still preventing resident visibility. The speaker notes this can be used for internal tasks like AGM checklists, inspections, fire reports, and quarterly reviews.</description></oembed>