Sometimes the recipient does not have ioMoVo access, or the content needs to live inside another site entirely. That is what links are for.

A CDN link serves the content through ioMoVo's delivery network, so it plays or downloads properly for whoever opens it, wherever they are. This is the right choice for a quick send to someone outside your organization.

You can set an expiration date and time when you generate a CDN link. Before that moment the link works normally; afterwards it stops.

This is the single most important habit in this article. A link works for whoever holds it, so a forwarded link opens just as well as the original. Expiry is what turns that from a permanent exposure into a temporary one, and it is far easier to set at creation than to remember to clean up later.

An embedded URL puts the content inside another page, so a video plays in your intranet, your CMS or a partner's site without anyone leaving it.

Think about lifespan before you embed. A link that ends up in a published page is one you will not easily retrieve, so consider whether an expiry that seemed sensible for an email is right for something meant to sit on a page for a year.

A link is not attached to a person, so it does not tell you who opened it and it does not stop being valid because someone left your organization. If you need either of those things, use a portal instead, which carries visitor login and an exportable activity log.

Links issued by a departing colleague do not expire when their account is disabled. They stay live until they hit their expiry or an admin ends them. This is exactly why setting expiry at creation is worth making a house rule rather than a case by case decision.

Which sharing method should you use compares all three routes. Removing a user's access covers the offboarding checklist in full.