Reference Glossary
Rights clearance
The process of confirming, before an asset is used, that every necessary licence, release, and permission for that use has actually been obtained and is currently valid.
Why it matters in a DAM
A DAM formalizes rights clearance as a workflow status attached to each asset — cleared, pending, expired — rather than treating an asset's mere presence in the system as proof it's safe to use, because assets routinely get uploaded before clearance is finished, and without an explicit status field a team has no way to distinguish an approved asset from one still awaiting a signed release.
A worked example
Common mistake
Assuming an asset is cleared for use simply because it exists in the DAM at all — assets are frequently uploaded during production, before the associated releases or licences are finalized, and a system without an explicit clearance status field gives teams no signal that the asset isn't actually approved yet.
Rights clearance is the confirmation step that everything needed to legally use an asset — copyright licence, model release, property release, attribution terms, territory scope — has actually been obtained, not just requested or assumed. It’s a process with a discrete outcome, not a permanent property of the file: an asset can be cleared for one use and not another, or cleared at one point in time and expired later.
The core DAM design problem is that clearance and ingestion happen on different timelines. Photos and video routinely enter the system during or immediately after a shoot, while releases are still being collected, contracts are still being countersigned, or a licence is still being negotiated. If the DAM treats “in the library” as equivalent to “cleared,” there’s no mechanism to stop someone from using a not-yet-cleared asset in the gap between upload and completed clearance.
A working rights clearance workflow needs an explicit status field — pending, cleared, expired, restricted — visible at the point of reuse, plus a way to flag downstream uses that depend on clearance completing. Without that, clearance becomes something that happened once during onboarding of an asset rather than a state the DAM actively tracks and enforces over the asset’s lifetime.
Frequently asked
What is rights clearance, precisely?
Rights clearance is the process of verifying, before an asset is used, that every permission required for that use has actually been obtained and remains currently valid — the copyright licence from the photographer or creator, model releases from recognizable people in the frame, property releases for trademarked logos, and synchronization rights from music copyright holders when a track is used. Confirmed and secured, not merely requested, negotiated, or assumed.
Why can't an asset's presence in the DAM be treated as proof it's cleared?
Uploading to a DAM is a technical act of saving a file into storage — it doesn't verify that any legal permission behind that file actually exists. Photos and video routinely enter the library during or right after a shoot, often before the photographer's licence is signed, model releases are collected, or rights negotiations conclude, and the same file can remain in the system after its licence has expired. Presence in the DAM alone says nothing about an asset's legal status.
What clearance statuses should a DAM track?
A DAM should track clearance as an explicit, dedicated field with distinct states — at minimum cleared, pending, expired, and restricted — rather than inferring legal status from an asset simply being present in the library. This status needs to stay visible at the moment someone is deciding whether to reuse an asset, not just get recorded once during initial onboarding, since clearance can lapse or change well after the asset was first uploaded.
Is clearance a permanent property of an asset once granted?
No — an asset can be cleared for one use and not another, or cleared at one point and expired later, so clearance needs to be tracked as an ongoing state, not a one-time event.
What's the risk of not having an explicit clearance status field?
There's no signal to distinguish an approved asset from one still awaiting a signed release, so a not-yet-cleared asset can be used in the gap between upload and completed clearance.
Why do ingestion and clearance often happen on different timelines?
Photos and video routinely enter the DAM during or right after a shoot, while releases are still being collected or contracts are still being countersigned — clearance frequently lags behind ingestion.