Stop sharing a recording without assuming copies vanish
Stopping future access is different from recovering a file someone already received. Begin by identifying where the recording was shared and which service controls each route.
Inventory the routes to the recording
List the hosted video page, any public link, named recipients, shared spaces and separate file attachments. Include duplicate uploads if the same lesson was published in more than one place. Changing one host does not automatically change another service or an emailed copy.
For example, a review video might have a named client invitation and also belong to a wider team space. Removing the client’s direct invitation may not be sufficient if the account still receives access through another permitted route. Check the actual sharing model instead of treating a recipient list as complete evidence.
Change the setting that actually grants access
Loom documents per-video permissions under Share and Link Settings, with additional options available there. Inspect that video’s current audience and remove or restrict the relevant route using the controls available to your role. If you cannot manage the route, ask the responsible owner or administrator.
Workspace defaults are a separate matter. Loom’s documentation says privacy defaults apply to new videos and do not change existing videos. Updating a default is therefore not a substitute for reviewing the particular recording you already shared.
- Identify the exact video and all known sharing routes.
- Inspect its current link, person and space permissions.
- Change the relevant access settings with an authorized account.
- Check the intended viewer result and document any unresolved route.
Verify without overclaiming the result
Test the link using an appropriate authorized viewer context. A page that no longer opens for one account is useful evidence about that route, not proof that every cached session, download or duplicate disappeared. Avoid making a universal instant-revocation promise.
If a recipient already downloaded the file or received an attachment, contact them through your normal process when removal is needed. A host permission cannot remotely erase an independent copy. Treat any sensitive-data incident according to your organization’s process rather than relying on a video setting alone.
Preserve what you still need
Restricting access, archiving content and deleting the original are different decisions. If the goal is simply to end a review period, avoid deleting the only source project before checking what you need to retain. Keep an approved internal copy where appropriate.
When sharing a replacement, review its permissions independently; a new upload may inherit defaults rather than the old video’s exact settings. Arte Soft publishes Reel. These are hosting and distribution decisions, not a claim that Reel controls or recalls copies after export.
Will changing workspace defaults close an old Loom link?
Not by itself. Loom documents those defaults as applying to new videos; inspect the existing recording’s permissions.
Can I erase downloaded copies by deleting the hosted video?
No. Independent files already delivered are separate from the hosted access you control.
