<?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/4d37266a0a5143b3a2d5bd9e8c45e688&quot; frameborder=&quot;0&quot; width=&quot;1670&quot; height=&quot;1252&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1252</height><width>1670</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1252</thumbnail_height><thumbnail_width>1670</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/4d37266a0a5143b3a2d5bd9e8c45e688-faf2154b9b827180.jpg</thumbnail_url><duration>449.219</duration><title>Tackling Subfolders and permission inheritance with Alloy</title><description>We worked on a project to let people put one folder inside of another. It was surprisingly tricky! This is mostly because it comes alongside a change to how our permissions model works. This talk goes over how our permissions model works, and then how we checked its soundness using model-checking software called Alloy.</description></oembed>