ioReports gives you a view of what has been happening across your content, which is useful both for day to day management and for showing an auditor that a library is actively governed.
What you can see
ioReports surfaces activity, including:
Uploads, so you can see what has come in and from where
Indexing, so you can confirm AI enrichment has run across a set
Comments and pins, which show where collaboration is actually happening
Chat activity against your assets
There is also per asset analytics, so you can look at a single item and see how it has been used rather than only aggregate numbers.
What it is for
The most common uses we see are working out which assets earn their storage cost, spotting content that was uploaded and then never touched, and confirming that a migration or a bulk index actually completed across everything you expected.
What to ask for if you need more
ioReports is activity reporting. If your requirement is something different, for example a formal access review for a specific control, say so explicitly when you raise it rather than asking for a report, because the two need different things from us.
Bring the control reference or the auditor's actual wording if you have it. That is usually enough for us to tell you quickly whether it is a configuration question, an export, or something we need to build.
Related
Roles, groups, and how access decisions are made covers how access itself is determined.