Reference Glossary
Collection (DAM)
A named grouping of assets pulled together for a specific purpose — a campaign, a client, a project — built from pointers to existing files, without moving or duplicating them.
Why it matters in a DAM
Collections let a user build a working set across the entire library regardless of where the assets actually sit or who owns them, e.g. pulling a logo, product shots and a video from six different folders into one "Q4 Launch" set. Because membership is reference-based, the underlying permissions and metadata stay on the original asset — the same file can belong to several collections at once without any duplication or version drift.
A worked example
Common mistake
Users assume deleting a collection can never affect the assets in it, but some DAM platforms allow collections to be configured with delete-cascading behavior depending on settings — teams should confirm the vendor's actual default before doing bulk collection cleanup, rather than assuming the safe behavior everywhere.
A collection groups assets for a specific purpose — a campaign, a client pitch, a product launch — by reference rather than by relocation. Adding a file to a collection doesn’t move it out of its folder or duplicate it; the collection is effectively a saved list of pointers to assets that live elsewhere in the library.
That reference-based design is what makes collections useful for cross-cutting work. A campaign lead can pull a hero image, three product shots and a video clip from six unrelated folders — owned by different teams, under different permission sets — into a single collection to share with an agency, without touching where any of those files actually live or who can edit them.
The behavior worth double-checking per platform is what happens on deletion. Because a collection is normally just a list, removing it should only remove the grouping, not the underlying assets — but exact behavior varies by DAM vendor and configuration, so teams doing a bulk collection cleanup should verify rather than assume before deleting anything at scale.
Frequently asked
What is a collection in a DAM, and how is it different from moving files?
A collection is a named grouping of assets built from pointers to existing files, not by moving or duplicating them. Adding a file to a collection doesn't relocate it -- the collection is effectively a saved list of references to assets that live elsewhere in the library.
Why are collections useful for cross-cutting work like a campaign?
A campaign lead can pull a logo, product shots, and a video from six different folders -- owned by different teams under different permissions -- into one "Q4 Launch" collection without touching where any of those files actually live or who can edit them.
Does deleting a collection delete the assets inside it?
By default the grouping is removed but source assets are untouched, since membership is reference-based. However, some DAM platforms allow collections to be configured with delete-cascading behavior depending on settings, so teams should confirm the vendor's actual default before bulk cleanup.
Can the same asset belong to multiple collections at once?
Yes -- because membership is reference-based, the underlying permissions and metadata stay on the original asset, so the same file can belong to several collections simultaneously without duplication or version drift.
How are collections typically shared externally?
Through a shareable link, optionally expiring or password-protected, letting an agency or client access the grouped assets without full DAM access.
What should a team verify before doing bulk collection cleanup?
Whether their specific DAM vendor's default behavior on collection deletion actually protects the source assets, since this varies by platform and configuration rather than being a universal guarantee.