Reference Glossary
Lightbox (asset selection)
A personal, per-user shortlist of assets flagged for review or reuse while browsing the DAM, borrowed from the physical light table photographers once used to sort slides side by side.
Why it matters in a DAM
DAM libraries can hold tens of thousands of assets, and users typically build a shortlist across several searches before deciding what to actually use — the same behavior as an e-commerce cart. Adobe's Experience Manager Brand Portal, for example, auto-creates one lightbox per logged-in user as their own working gallery, which confirms this is deliberately a per-person working area, distinct from a shared, named collection the whole team can see.
A worked example
Common mistake
Teams rely on a personal lightbox as if it were shared project storage, then lose the shortlist when the user's account is deactivated or a session clears, because lightbox contents are rarely covered by the same governance and retention rules as a named, team-owned collection.
A lightbox is a personal shortlist — assets a single user flags while browsing or searching, kept separate from any shared team object. The name comes from the physical light table photographers historically used to lay slides side by side for comparison before making a final selection; the DAM feature does the same job digitally, one user at a time.
In practice it behaves like an e-commerce shopping cart: a user runs several searches, stars or adds candidates from each, and only later decides which of them to actually use, share or download. Adobe Experience Manager’s Brand Portal makes the per-user nature explicit — every logged-in user gets their own automatically-created lightbox as a personal gallery, separate from any named, shared collection other users can see.
Because a lightbox is informal and tied to one account, it isn’t a substitute for a governed collection. If a shortlist needs to survive beyond one person’s login — for handoff to a colleague, for an audit trail, or simply so it doesn’t vanish when the user’s account is deactivated — it needs to be promoted into a named collection with its own permissions, not left as a personal lightbox.
Frequently asked
What is a lightbox in a DAM, and where does the name come from?
A lightbox is a personal shortlist of assets a single user flags while browsing or searching. The name comes from the physical light table photographers historically used to lay slides side by side for comparison before making a final selection.
How does a lightbox behave compared to an e-commerce cart?
Similarly -- a user runs several searches, stars or adds candidates from each, and only later decides which of them to actually use, share, or download, rather than deciding at the moment of each individual search.
Is a lightbox shared with the rest of a team?
No -- it's personal and tied to one user's account, distinct from a shared, named collection the whole team can see.
What example confirms lightboxes are deliberately per-user?
Adobe Experience Manager's Brand Portal auto-creates one lightbox per logged-in user as their own personal gallery, separate from any named, shared collection other users can see.
What's the risk of relying on a personal lightbox as shared storage?
Teams that treat it as project storage lose the shortlist when the user's account is deactivated or a session clears, because lightbox contents are rarely covered by the same governance and retention rules as a named, team-owned collection.
What should happen to a lightbox shortlist that needs to survive beyond one person?
It should be promoted into a formal named collection or converted into a download batch once finalized, since a lightbox isn't a substitute for a governed, shareable object.
Sources
- Adobe Experience Manager Brand Portal automatically creates one lightbox per logged-in user as their own personal gallery. checked 2026-08-07 — Adobe Experience League — Manage the Lightbox Collection