<?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/aa5f86b1f0534bcd85dc1d915a86effa&quot; frameborder=&quot;0&quot; width=&quot;1874&quot; height=&quot;1405&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1405</height><width>1874</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1405</thumbnail_height><thumbnail_width>1874</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/aa5f86b1f0534bcd85dc1d915a86effa-b3b58ce2189c4daf.gif</thumbnail_url><duration>217.957</duration><title>How to Control Visibility of Systems</title><description>This Loom explains how visibility works for systems, policies, and trainings based on permission levels. It covers four access tiers: administrators and editors can see everything in an account, while contributors and readers only see assigned items. The presenter shows that visibility is granted either by assigning a person directly in members or by assigning systems and related content to a role, which then grants access to anyone in that role. An example is given where Amy, previously a contributor without visibility, can see the newly assigned item after direct assignment.</description></oembed>