Reference Glossary
Licence tier
A pricing and rights structure offering multiple package levels for the same asset — for example web-only, extended, or print — each unlocking a different scope of permitted use.
Why it matters in a DAM
A DAM has to track which tier was actually purchased, because upgrading how an asset is used — moving a web-tier photo onto packaging, or exceeding a print-run cap tied to a lower tier — without buying the higher tier is a licence violation even though the asset itself never changed. Teams that only record "licensed: yes" have no way to catch that the use has outgrown what was paid for.
A worked example
Common mistake
Treating "we downloaded it from the licensed stock library" as automatic coverage for any use, when only the basic web tier was purchased — and later putting the same image on product packaging or a large print run that the tier never authorized.
A licence tier is a packaging structure many stock and content providers use to sell the same underlying asset at different price points, each covering a different scope of use — a basic tier might cover web and social use up to a certain reach, while an extended or print tier adds packaging, merchandise, or unlimited print runs at a higher price. The asset file itself doesn’t change between tiers; the permitted use does.
This is a common source of DAM rights drift, because the asset that was downloaded under a basic tier looks and behaves identically to one licensed at the extended tier — nothing about the file signals which tier was actually purchased. If the DAM doesn’t record the tier explicitly, a team reusing the asset months later for a bigger project has no way to know it’s now outside the scope of the original purchase.
The fix is treating tier as a first-class rights field, not an assumption baked into “we have a licence for this,” and flagging when a proposed new use — packaging, large print run, merchandise — exceeds what the recorded tier covers.
Frequently asked
What is a licence tier?
A packaging structure where the same underlying asset is sold at different price points — for example web-only, extended, or print — each unlocking a different scope of permitted use, without the file itself changing.
Why can't you tell which licence tier was purchased just by looking at the file?
The file itself carries no signal of which tier applies. A web-only download and an extended-licence download of the same asset are identical in resolution, format, and appearance. Licence tier isn't a property of the image; it's metadata describing the scope of usage rights purchased alongside it. Opening or inspecting the asset gives no indication of what use is actually permitted, so that information has to live in the DAM's rights record, not in the pixels.
What happens if an asset's use grows beyond the tier that was actually purchased?
Nothing about the file changes, but the use itself becomes a licensing violation. For example, moving a web-tier image onto product packaging or into a large print run without buying upgraded rights exceeds what was authorized. This exposes the organization to a claim from the rights holder or stock agency, and licence agreements typically allow for retroactive fees, forced upgrades, or contractual penalties once usage is found to exceed the tier that was actually purchased.
What's the risk of recording only "licensed: yes" for a tiered asset?
A flat "licensed: yes" flag confirms only that some rights exist, not what those rights actually cover. It discards the detail of the permitted scope, whether use is limited to web, capped at a specific number of views, or excludes print and packaging entirely. Without that detail recorded, the organization has no way to check whether a proposed or existing use still falls within the boundaries of what was actually purchased for that asset.
How should licence tier be treated in a DAM's rights metadata?
Licence tier should be captured as a structured, dedicated metadata field rather than a free-text note or comment attached to the asset. That field needs explicit, checkable boundaries, for example editorial-use-only, a cap such as up to 500,000 views, or a defined list of permitted channels. Structuring it this way lets the DAM flag proposed uses that fall outside those limits, instead of relying on someone remembering or re-reading the original licence document.
What's a typical example of tier-related misuse?
Treating "we downloaded it from the licensed stock library" as automatic coverage for any use, when only the basic web tier was purchased, then later putting the same image on packaging or a large print run.