{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/aa5f86b1f0534bcd85dc1d915a86effa\" frameborder=\"0\" width=\"1874\" height=\"1405\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1405,"width":1874,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1405,"thumbnail_width":1874,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/aa5f86b1f0534bcd85dc1d915a86effa-b3b58ce2189c4daf.gif","duration":217.957,"title":"How to Control Visibility of Systems","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."}