Getting started
Your first week
A suggested rollout plan for a new workspace.
You don't have to follow this. It's the order that tends to produce the fewest surprises when a team adopts Inverity on a real library.
Day 1 — connect and sample
Connect one source and point Inverity at a single folder you know well. Ten to fifty assets is plenty.
Look at the results screen and check three things:
- The savings rate. What percentage came off, on average?
- The skips. How many assets were kept as originals, and does that make sense for the content? (Already-optimized files legitimately skip.)
- The output. Open two or three optimized files next to the originals at full size. This is the only quality check that matters.
Day 2 — set your profile
If the output looks right, leave the default profile alone. If you want smaller files and this content can take it, move to a more aggressive profile. If this is product photography or archive material, move conservative.
Profiles are set per connected source, so you can be aggressive on marketing imagery and conservative on your DAM masters at the same time. See Quality and profiles.
Day 3 — estimate your volume
Take the source size of the folder you sampled and extrapolate to the library you actually want covered. Compare that against your plan's monthly volume.
Two numbers matter, and they're different:
- The backfill — a one-time cost to process what already exists.
- The steady state — how much new media your team adds each month.
Your plan needs to cover the steady state permanently, and the backfill once. It is common to upgrade for one month to clear a backlog, then settle a tier lower. See Volume and usage.
Day 4 — widen the scope
Add the rest of your high-value locations. Kick off backfills in batches rather than all at once, so you can watch the volume meter move.
Day 5 — bring in the team
Invite the people who need to see results, with the least access they need. Reviewers and stakeholders generally want view access, not admin. See Team and roles.
Turn on two-factor authentication for everyone with admin access — that account can reach your connected platforms' tokens. See Security.
Clear your CDN once
If your optimized images aren't visibly smaller in a browser test, your CDN or page cache is almost certainly still serving the old copies. The file in your platform is already replaced. Purge the cache once, then re-test. See Delivery and caching.
After the first week
Check the usage meter weekly for the first month until you know your steady-state rate. After that, the only routine work is watching for skipped — not smaller rates that suddenly change, which usually means someone started uploading pre-compressed exports.