<?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/14b08f3a08fc44a49ed6ea95e1731eff&quot; frameborder=&quot;0&quot; width=&quot;2228&quot; height=&quot;1671&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1671</height><width>2228</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1671</thumbnail_height><thumbnail_width>2228</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/14b08f3a08fc44a49ed6ea95e1731eff-cf868c66da4ada08.gif</thumbnail_url><duration>221.1264</duration><title>Managing Gated Content in Webflow CMS: Best Practices 🔒</title><description>In this video, I address a question about managing public and gated content in a CMS collection. I suggest adding a Boolean field in Webflow to differentiate between paid and free content, which would allow us to exclude links to gated pages for logged-out users. I also touch on the importance of hiding premium content using CSS for added security. If you need further clarification or a demo, please let me know. Ultimately, it&apos;s crucial to understand that if someone is determined to access gated content, they can still do so with a simple payment.</description></oembed>