Current Limitation: When uploading assets to the DAM, users must manually add and populate metadata fields after the upload is complete. There is no ability to pre-configure or auto-attach specific fields during the upload process, and required fields cannot be scoped to specific folders or asset types — they apply globally or not at all.
Use Case: Many organizations rely on specific metadata fields to drive downstream integrations (e.g., web publishing, POS delivery, SFTP triggers). During mass uploads, users frequently forget to attach these fields or spend significant time manually adding them post-upload. This creates incomplete metadata, delays integration workflows, and undermines data governance. Ideally, administrators should be able to define which fields are automatically present on every asset uploaded to a given folder or asset type — even if the field value is left blank for the user to populate later.
Requested Enhancement: Allow administrators to configure field templates per folder or asset type that auto-attach specified metadata fields (with default or blank values) to every asset uploaded to that location.
Expected Impact: Eliminates a common source of incomplete metadata, reduces post-upload rework, ensures integration-readiness from the moment of upload, and enforces consistent data governance across teams.