Acquia DAM (Widen) Administrator study materials
Acquia DAM (Widen) Administrator study resources

Acquia DAM (Widen) Administrator: Digital Asset Management (DAM) Administration on Acquia/Widen

Acquia DAM (Widen) Administrator · Work through your exam, one topic at a time.

All guide sections

Digital Asset Management (DAM) Administration on Acquia/Widen

What the domain covers

Widen (now part of Acquia) organizes assets around a few core objects you must be able to reason about: assets (the files themselves), metadata fields attached to them, categories (the hierarchical taxonomy used for browse/search), collections (curated groupings, often used for sharing), and users/groups with roles and permissions. Administration means governing metadata structure, taxonomy, upload/ingest behavior, permissions, and the search/browse experience.

Concepts you must know

Understand the difference between controlled-vocabulary metadata (fixed dropdowns/taxonomy) and free-text fields; controlled values are what make filtering and reporting reliable. Know that categories drive navigation and are usually hierarchical, while collections are lightweight and often used for delivery/sharing rather than permanent taxonomy. Understand permission models: role-based access, group membership, and how permissions can be scoped to assets or collections. Know that derivatives/versions are generated from originals and that deleting or replacing an original has downstream effects on links and embedded assets. Understand embed links and public/private sharing and why expiring or restricted links matter for governance.

Traps in exam questions

  • Confusing categories (taxonomy) with collections (curation/sharing).
  • Assuming deleting an asset only removes the file, when it also affects links, versions, and metadata relationships.
  • Assuming permissions are purely per-user when groups/roles usually drive access.
  • Treating free-text fields as reliable filters when only controlled values are.

Rule of thumb

If a question asks how users will find assets, think metadata + categories + search. If it asks how users will receive assets, think collections + permissions + link settings. Worked example: to let an external partner download only a campaign subset, create a collection, grant that group access, and share via a controlled link rather than loosening global category permissions.