<?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/b65354b89d154f8bbfe08e66c8a52116&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/b65354b89d154f8bbfe08e66c8a52116-60f31bc29951ccd4.gif</thumbnail_url><duration>30.859</duration><title>Verifying Resource Access After Publishing</title><description>This Loom checks that the latest database publish behaves correctly with resource access. The author confirms they cleared the database with no resource access and then published again. They note there is no error because the email was already present. Finally, they observe a single resource access result that includes both the node and resource access.</description></oembed>