Reference Glossary
Rights holder
The person or entity that legally owns the copyright or other exclusive right in an asset, who may or may not be the original creator — for example an employer under work-for-hire, or an agency after a rights transfer.
Why it matters in a DAM
A DAM's rights holder field is who legal actually contacts for licence renewal, clearance questions, or a takedown, and it needs to be distinguished from a "photographer" or "contributor" credit field, because rights can be assigned or transferred while the original creator's name stays attached to the file for attribution purposes — collapsing the two into one field means the DAM points clearance requests at the wrong party after any transfer.
A worked example
Common mistake
A DAM system stores only a single "photographer" field and uses it for both credit and rights contact purposes, so after a freelancer's work is bought out by an agency or the company itself under a work-for-hire agreement, licence renewal requests still get routed to the original photographer instead of the actual current rights holder.
The rights holder is whoever currently holds the exclusive legal rights in a work — most often copyright, though other exclusive rights can also apply. This is frequently, but not always, the person who created the asset: under work-for-hire arrangements, the employer or commissioning party is typically the rights holder from the moment of creation, and rights can also be sold or assigned afterward, moving the rights holder away from the original creator entirely.
This distinction matters for DAM design because “who made this” and “who has the right to license this” are different questions that a single “photographer” or “creator” field can’t answer correctly. A photo credit should stay attached to the actual photographer for attribution purposes even after the rights are sold, while a separate rights holder field needs to update to reflect whoever now controls licensing decisions.
The practical consequence of getting this wrong shows up during any rights-related event — a licence renewal, a clearance request, a dispute — when the DAM points the request at a contact who no longer has authority to answer it, because the underlying rights changed hands without the metadata being updated.
Frequently asked
Is the rights holder always the same person as the creator?
No — under work-for-hire arrangements the employer or commissioning party is typically the rights holder from the moment of creation, and rights can also be sold or assigned afterward to someone else entirely.
Why should "photographer" and "rights holder" be separate DAM fields?
Because a photo credit should stay attached to the actual photographer for attribution purposes even after rights are sold, while the rights holder field needs to update to reflect whoever currently controls licensing decisions.
What goes wrong when a DAM stores only one "photographer" field for both purposes?
After a freelancer's work is bought out by an agency or the company under work-for-hire, licence renewal requests keep getting routed to the original photographer instead of the actual current rights holder.
What is the rights holder field used for in day-to-day DAM operations?
It's who legal actually contacts for licence renewal, clearance questions, or a takedown — the practical contact point for anything rights-related.
Can rights holder status change without the original creator's name changing in the DAM?
Yes — rights can be assigned or transferred while the original creator's name stays attached to the file for attribution, so the rights holder field needs independent updates when that transfer happens.
What's the consequence of not updating the rights holder field after a transfer?
During any rights-related event — renewal, clearance, dispute — the DAM points the request at a contact who no longer has authority to answer it.