<?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/7a089535233d43af90053e3dc3d119a2&quot; frameborder=&quot;0&quot; width=&quot;1910&quot; height=&quot;1432&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1432</height><width>1910</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1432</thumbnail_height><thumbnail_width>1910</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/7a089535233d43af90053e3dc3d119a2-4bdefb1022dad75f.gif</thumbnail_url><duration>482.937</duration><title>Hide Unassigned Content Request Errors Explained</title><description>This Loom explains an edge case where learners see an error when requesting access to content that they are not allowed to view. The presenter reviews two learner control settings, noting that if self-assignment is enabled, learners can assign themselves and no approval request is created. The main focus is the hide unassigned content option: while admins and managers can still see everything, learners who access unassigned content by mistake will see missing data and will receive an “error sending request” when they try to request access. When the flag is turned off, the same learner can load the content and successfully send the request, confirming the system is working as intended.</description></oembed>