If your editors are already living in Premiere, Media Composer, or Final Cut, the fastest way to get value from ioMoVo is to bring the library to them rather than asking them to change how they work.

ioMoVo has native plugins for:

There is also a desktop app for people who want a local window onto the library without opening a creative application at all.

The point of the plugin is that an editor can search the library, find the shot, and bring it into a timeline without leaving the application or going hunting through a shared drive. Because ioMoVo has already indexed and enriched the content, the search is against what is actually in the footage rather than against whatever the file happened to be named.

Permissions follow the person, not the plugin. An editor sees what their role and group membership allow them to see, the same as they would in the browser.

For large formats, editors normally work against proxies and relink to the originals at finish. This is worth agreeing as a house rule early, because it is the single biggest factor in how responsive the workflow feels on a busy project.

Plugin installation depends on your deployment and on how your organization distributes creative tooling. Talk to your ioMoVo contact or your systems administrator, who will have the right installer for your environment. In an air gapped deployment the plugins are fully supported, they just arrive through your own transfer process rather than an outbound download.

The usual causes, in order of how often we see them: the user is signed in to an account that is not a member of your tenant, the machine cannot reach the ioMoVo endpoint, or the user genuinely does not have access to the collection they are looking for. Check tenant membership first.