Acquia DAM (Widen) Administrator key terms

A system for storing, organizing, finding, and distributing digital files such as images, video, and documents, along with the metadata and permissions that govern their use.

A single stored digital file in the DAM, such as a photo, video, PDF, or audio clip, together with its metadata, versions, and associated permissions.

Structured descriptive information attached to an asset, such as title, keywords, rights, and dates, that makes files searchable, governable, and reusable.

Metadata written inside the asset file itself (for example IPTC or XMP fields), which travels with the file when downloaded or shared outside the DAM.

An extensible metadata standard from Adobe that stores descriptive and rights information inside many file types, commonly read and written by DAM tools during import and export.

The overall hierarchical structure of categories used to classify assets in the DAM, defining parent-child relationships and the vocabulary the organization standardizes on.

A node in the DAM taxonomy used to group related assets, often nested under parent categories, so users can browse and filter content by subject or business function.

A predefined, approved list of terms used for a metadata field so that values stay consistent, avoiding free-text variants and improving search and reporting accuracy.

A descriptive word or short phrase applied to an asset to improve findability, often drawn from a controlled list or entered freely depending on field configuration.

A curated grouping of assets assembled for a purpose such as a campaign or project, which can span categories and is often shared with specific users or groups.

A distinct iteration of an asset stored under the same asset record, letting administrators and users compare or revert to earlier renditions without creating duplicate records.

A derived output of an asset in a specific format, size, or crop, generated by the DAM so users can download an appropriately formatted file without manual conversion.

A configuration that determines how incoming files are processed on upload, including which metadata fields are applied, which conversions run, and where assets are filed.

The process of bringing files into the DAM, whether by manual upload, watched folder, or integration, during which metadata and processing rules are applied.

A defined set of users granted specific rights to assets, categories, or system functions, used to control who can view, edit, download, or administer content.

A named bundle of permissions assigned to users, such as administrator, editor, or viewer, that determines which actions a user may perform in the DAM.

The degree of rights a user or group holds over a given asset or area, ranging from no access through view, edit, and full administrative control.

A branded, externally facing site built from DAM content that lets selected audiences browse and download approved assets without direct access to the full DAM interface.

A public-facing or partner-facing web destination that presents approved brand assets, guidelines, and downloads, typically configured and maintained by DAM administrators.

The DAM function that locates assets by matching query terms against metadata, filenames, and sometimes file contents, often combining keywords with filters and facets.

A filter dimension shown alongside search results, such as category, file type, or date, that lets users narrow a result set by selecting specific values.

A configured sequence of steps, approvals, or automated actions that assets pass through, such as review before publishing or routing for metadata completion.

A workflow state in which designated reviewers confirm an asset is ready for use or distribution, often gating download or portal publication until granted.

The practice of recording and enforcing usage rights, licenses, and expiration dates for assets so the organization knows where and how long content may be used.

A configured date or condition after which an asset or its rights are no longer valid, commonly used to automatically flag or archive outdated content.

An automated transformation applied to an uploaded asset, such as resizing, format change, or watermarking, producing renditions for downstream use.

A visible or invisible mark overlaid on an asset rendition to indicate ownership or restrict unauthorized use, often applied automatically to preview or unapproved files.

A chronological record of actions taken in the DAM, including who changed what and when, used for accountability, troubleshooting, and compliance reporting.

A credential issued to an application or integration that authenticates programmatic requests to the DAM, controlling which data and operations the integration may access.

A configured connection between the DAM and another system, such as a CMS or ecommerce platform, that exchanges assets and metadata automatically.

Acquia's hosted environment for building, deploying, and managing Drupal and other web applications, providing infrastructure, tooling, and operational workflows.

A distinct instance of an application within a hosting platform, such as development, staging, or production, each with its own code, configuration, and data.

The process of moving code or configuration from one environment to another, typically from a lower environment up to production, following a defined release process.

The version-controlled repository of application code and configuration that is built and deployed to hosting environments.

A distributed version control system used to track changes to code and configuration, and the standard mechanism for triggering deployments on Acquia's platform.

A command-line interface for managing Drupal applications, used for tasks such as cache clearing, database updates, and configuration import during administration and deployment.

An open-source content management framework on which many Acquia-hosted sites are built, organized around modules, themes, and configuration entities.

A packaged extension that adds or alters functionality in a Drupal application, enabled and configured per environment as part of the site build.

The practice of exporting and importing site configuration as version-controlled files so settings move predictably between environments alongside code.