Reference Glossary
Embargo
A time-based restriction preventing an asset from being published, downloaded, or otherwise used until (or after) a specified date, commonly applied to press images, product launch materials, or unreleased content.
Why it matters in a DAM
DAMs implement embargoes as system-enforced date fields tied to access permissions — press and partner users get pre-launch access to product photos under embargo, and the DAM is set to auto-release (or continue blocking) the asset at a precise date and time rather than relying on people to remember and manually flip access. Product-launch press embargoes are broken often enough in the tech and consumer industries that access-control failures around embargo dates are a recognized, recurring operational risk, not a hypothetical one.
A worked example
Common mistake
Setting an embargo date without specifying a timezone. When a global press list spans regions, the asset unlocks hours early for some outlets and hours late for others relative to the intended simultaneous release moment — a recurring problem in coordinated global product launches.
An embargo restricts an asset by time rather than by scope or geography: the asset exists in the DAM, may even be visible to a specific group of users, but publication or download is blocked until a set date and time. This is most common in PR and product-launch workflows, where journalists, reviewers, or retail partners need pre-release access to product photography or video to prepare coverage, but are contractually bound not to publish before an agreed date — the embargo.
In a DAM, an embargo is typically enforced two ways at once: an access-control layer restricts which user groups can even see the asset before the embargo lifts (usually a vetted press or partner list), and a scheduling mechanism automatically changes the asset’s visibility or download permission at the embargo date without requiring manual intervention. Some DAMs extend this to public-facing pages as well, holding a press release or product page in a draft state that auto-publishes at the embargo moment.
The operational risk sits almost entirely in timing precision. Embargoes coordinated across international press lists need an unambiguous timezone (or, more reliably, a UTC timestamp the DAM converts locally), because a vague ‘releases September 15’ invites outlets in different regions to publish hours apart from each other — undermining the entire point of a coordinated embargo. Embargo breaks, whether accidental or deliberate, are a well-known recurring issue around major product launches in the technology press.
Frequently asked
What is an embargo in a DAM context?
A time-based restriction preventing an asset from being published, downloaded, or otherwise used until (or after) a specified date, commonly applied to press images, product launch materials, or unreleased content.
How do DAMs typically enforce embargoes?
As system-enforced date fields tied to access permissions — press and partner users get pre-launch access to product photos under embargo, and the DAM is set to auto-release (or continue blocking) the asset at a precise date and time rather than relying on people to remember and manually flip access.
How common is it for embargoes to actually fail in practice?
Product-launch press embargoes are broken often enough in the tech and consumer industries that access-control failures around embargo dates are a recognized, recurring operational risk, not a hypothetical one.
What's a specific mistake that breaks embargo timing?
Setting an embargo date without specifying a timezone. When a global press list spans regions, the asset unlocks hours early for some outlets and hours late for others relative to the intended simultaneous release moment — a recurring problem in coordinated global product launches.
Who typically needs pre-launch access to an embargoed asset?
Press and partner users, who are granted access ahead of the embargo's public release date so they can prepare coverage, while the DAM still blocks general publication or download until the embargo lifts.
How can a DAM avoid the timezone problem with global embargoes?
By setting the embargo release moment with an explicit timezone (or a fixed UTC instant) rather than a bare date, so the asset unlocks at the same absolute moment for every region instead of drifting relative to local time.