DAM by Industry and Role

You often can, and the question is which department pays for the compromise. Problems appear where a sector has a hard requirement the general platform treats as optional — technical file previews, per-project rights, or retention rules. It is worth checking those specific requirements before standardising rather than after.

File size and interdependence. Design files reference other files, previews are expensive to generate, and the authoritative version of a drawing matters legally rather than merely practically. Platforms that treat every asset as a self-contained image handle this poorly, which our AEC material covers in detail.

Separation by client and evidence of delivery. Agencies hold assets belonging to several clients under different terms, and need to show what was delivered, when and under which licence. Access boundaries and audit trails matter more than they do for a team that only ever works on its own brand.

Usually both, doing different jobs. Version control handles the build and its source files; the DAM handles the assets that surround it — concept art, marketing captures, trailers, store assets — where the audience is wider and the rights matter. Our game development material covers where the boundary sensibly falls.

Governance stops being optional. At a few dozen users a shared convention holds; at a few thousand it does not, and the system has to enforce what the convention used to. Role design, delegated administration and audit become the deciding criteria rather than the search interface.

By treating location as a first-class metadata field rather than as something buried in a filename. Assets tied to sites, surveys or projects need that link preserved through export, which not every platform does. Our GIS material covers the practical workflow.

Both, and the label is unreliable. Some platforms are genuinely built around a sector's workflow; others are general systems with a sector page on the website. The test is whether the sector's hard requirement is a feature or a workaround you would have to build.

In how long they last and who is liable. Agencies and publishers manage licences that expire and belong to third parties; in-house teams more often own their assets outright. Expiry tracking is essential in the first case and optional in the second.

Preview generation for technical formats, retention rules, and export of metadata to downstream systems. All three are invisible in a demo and expensive to discover after migration, because each one is a property of the file pipeline rather than the interface.

A shared core can, with department-specific extensions on top. What fails is forcing every team into one flat vocabulary: terms proliferate to cover the gaps and search stops discriminating. A small governed core with controlled extensions holds up better.