Reference Glossary
Asset embargo release
An asset embargo release is the point at which a DAM lifts a publication hold on an asset, making it usable only after a set date, approval, or triggering event rather than immediately upon upload.
Why it matters in a DAM
PR, publishing, and marketing teams routinely load embargoed assets — product photography ahead of launch, earnings graphics, press images — so partners can prepare coverage in advance, but the assets must not go live before the embargo lifts. The protection only works if the hold is enforced by the DAM's permission system (a locked date field plus restricted download access) rather than a note in an email or a caption, because once an asset is downloaded the DAM has no further control over where it's used, so honoring the embargo depends entirely on gating access beforehand, not on trusting recipients to wait.
A worked example
Common mistake
The embargo date is written into the asset's caption or a shared spreadsheet instead of set as an access-control field in the DAM, so the file stays fully downloadable by anyone with the share link days before the embargo lifts, and it leaks early.
An embargo is a hold on publication — a supplier, agency, or company shares an asset ahead of time so recipients can prepare, on the condition that nothing goes public before a set date. In a DAM, that condition only holds if the system enforces it structurally: a locked “embargo until” field paired with a permission group that blocks download or public visibility until that timestamp passes. Treating the embargo date as descriptive metadata — visible in a caption or a shared note but not actually gating access — relies entirely on every recipient’s good faith, which is a weak control for anything commercially or reputationally sensitive.
- A locked “embargo until” date/time field on the asset record
- A restricted permission group blocking download or public visibility until that timestamp passes
- An audit log recording every access attempt before release
- Either an automated visibility change at the embargo timestamp, or a manual release step tied to confirming the triggering event actually happened
The release itself is usually one of two things: an automated event, where the DAM flips the asset’s visibility or permission group the moment the embargo timestamp passes, or a manual action, where an admin explicitly releases the hold after confirming the triggering event (an earnings call finishing, a product officially launching) actually happened. Automated release is cleaner for date-certain embargoes; manual release is safer when the trigger is an event rather than a fixed time, since a DAM has no way to know on its own whether a press conference actually started on schedule.
Because an embargoed asset is often shared with external partners before release, the DAM’s audit log — who accessed it, when, and whether the embargo field was ever modified — becomes the practical record if an embargo does break, useful for figuring out whether the leak came from inside the controlled group or from the asset circulating after legitimate release.
Frequently asked
What's the difference between an embargo and a general usage restriction?
An embargo is a time-based publication hold that lifts automatically or on a triggering event; a usage restriction (like editorial-only or a licensing window) can remain in force indefinitely and doesn't necessarily involve a release date.
Can a DAM automatically publish an asset once the embargo date passes?
Many platforms support scheduled visibility changes tied to a date field, so the asset moves from a restricted group to a public or general collection automatically — though some teams prefer a manual release step as a final check.
Who should have access to an embargoed asset before it lifts?
Only the specific group that needs it for preparation — press partners, retail buyers, internal reviewers — added explicitly to a restricted permission group rather than a broad or default-access folder.
What should happen if an embargoed asset leaks before the release date?
The DAM's access log should be reviewed to identify who downloaded it and when, since that's usually the only way to trace whether the leak originated from within the pre-release group or from an asset that was already released.
Should embargo dates be set per-asset or per-collection?
Per-asset is safer when different items in a batch have different release timing (some renders ready earlier than others); per-collection is simpler when an entire set genuinely shares one release moment.
Is an embargo release the same as a license or rights expiration date?
No — an embargo controls when an asset may first be published, while a rights expiration date controls when an asset must stop being used; a single asset can carry both, at different points in its lifecycle.