If you are new to ioMoVo, it helps to know what the main areas do before you start moving files around. Here is the short version.
Where your content lives
ioCloud holds the assets stored in ioMoVo itself. ioHub connects to storage you already own and to the other systems your team works in, so content that lives elsewhere is still searchable and usable without being copied in.
That distinction matters more than it sounds. A lot of what ioMoVo does is let you work across both without a migration project first.
Where you get work done
ioProject is a shared workspace for a piece of work. You pull in the files that belong to a project and they stay exactly where they already are, in ioCloud or in a connected source. A project carries its own members, open tasks, and file count, and you can archive it when the work is finished.
ioPilot is the assistant. You ask it to find, analyze, or organize assets, and it works inside whatever scope you have selected. You can point it at a project, at a folder, or across everything you have access to.
Where you share and report
ioPortal is how you present a curated set of assets to people outside your team, using templates you can reconfigure yourself.
ioReports shows what has been happening: uploads, indexing, comments, pins, and chat activity.
Where you extend it
ioMarket is the catalog. It has three parts: integrations and add ons for connecting storage, AI services, and other tools; playbooks, which are prepackaged domain knowledge you can switch on; and an asset marketplace for licensed stock content.
A note on naming
Product surfaces carry the io prefix. Admin settings use plain English, so you will see Governance and Taxonomy rather than ioGovernance.
Where to go next
If you are setting ioMoVo up for the first time, start with your deployment model and your storage connections. If you are joining a workspace someone else set up, start with ioProject and ioPilot.