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?
Because the asset downloaded under a basic tier looks and behaves identically to one licensed at an extended tier — nothing about the file itself signals which tier applies.
What happens if an asset's use grows beyond the tier that was actually purchased?
It becomes a licence violation, even though the asset itself never changed — for example moving a web-tier photo onto packaging without buying the higher tier.
What's the risk of recording only "licensed: yes" for a tiered asset?
The DAM has no way to catch that a proposed new use — packaging, large print runs, merchandise — exceeds what the recorded tier actually covers.
How should licence tier be treated in a DAM's rights metadata?
As a first-class rights field on its own, not an assumption folded into a general "we have a licence for this" flag.
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.