A saved search stores the query itself \u2014 the keywords, filters, and facet selections a user assembled \u2014 so it can be re-run later with one click instead of being rebuilt from scratch. Because it re-executes the search rather than storing a fixed list of results, a saved search always reflects the library as it currently stands, the same way a smart collection does. The practical difference is scope and intent: a saved search is typically a personal convenience tool, while a smart collection is usually built to be a shared, named resource other people browse.<\/p>
In day-to-day DAM use, saved searches are what let a repeat task \u2014 a photo editor pulling this week’s newly approved product shots, a legal reviewer checking assets nearing rights expiry \u2014 stay a one-click action instead of a five-filter reconstruction every time. That efficiency gain is small per use but compounds across a team doing the same lookup daily.<\/p>
The failure mode is almost always a scoping assumption: someone treats their own saved search as institutional knowledge and references it in a process document, not realizing colleagues can’t see it without an explicit share. Teams that want a search to function as shared infrastructure should promote it to a smart collection rather than rely on saved-search visibility defaults.<\/p>","protected":false},"excerpt":{"rendered":"
A stored search query \u2014 keywords, filters, and facets \u2014 that a user can re-run on demand, without it acting as a shared, always-updating collection object.<\/p>\n","protected":false},"author":0,"featured_media":0,"template":"","meta":{"footnotes":"","faq":[{"question":"What is a saved search?","answer":"A saved search stores a query \u2014 keywords, filters, and facet selections \u2014 so it can be re-run with one click instead of being rebuilt from scratch each time, for example brand:Acme AND usage_rights:web AND resolution:>3000px."},{"question":"Is a saved search the same as a smart collection?","answer":"No. Both re-run live against the current library rather than storing a fixed list of results, but a saved search is typically a personal convenience tool scoped to the user who created it, while a smart collection is usually built to be a shared, named resource other people browse."},{"question":"Who can see a saved search by default?","answer":"Only the user who saved it, unless it's explicitly shared. Most DAM platforms default saved searches to private."},{"question":"What mistake do teams make around saved-search visibility?","answer":"Someone references a colleague's saved search, like \"the hero images search\", in a process document or workflow, only to find it doesn't exist for anyone else because it was never explicitly shared or promoted."},{"question":"How should a team make a search available to everyone?","answer":"Promote it to a smart collection rather than relying on saved-search visibility defaults, since a saved search is meant as a personal shortcut, not shared infrastructure."},{"question":"What kind of DAM tasks benefit most from saved searches?","answer":"Repeat lookups like a photo editor pulling this week's newly approved product shots, or a legal reviewer checking assets nearing rights expiry \u2014 a small time savings per use that compounds across a team doing the same lookup daily."}],"checked_date":"2026-08-07","sources":[],"kicker":"","fact_checker":0,"reading_time":0,"revisions":[],"seo_title":"","seo_description":"","noindex":false,"related":[2459,2458,2467,2455,2461,2399],"definition":"A stored search query \u2014 keywords, filters, and facets \u2014 that a user can re-run on demand, without it acting as a shared, always-updating collection object.","why":"A DAM user who regularly needs the same slice of the library \u2014 say, brand = Acme AND resolution > 3000px AND usage_rights = web \u2014 doesn't want to rebuild that filter combination every session, so saving it as a query saves repeated setup work. Unlike a smart collection, most DAM platforms scope a saved search to the individual account by default, so it's a personal shortcut rather than a shared team resource.","example_rows":[{"field":"Query","values":"brand:Acme AND usage_rights:web AND resolution:>3000px"},{"field":"Scope","values":"Visible only to the user who saved it, unless explicitly shared"},{"field":"Behavior","values":"Re-runs the search live each time it's opened; not a stored asset list"}],"mistake":"A team member assumes a colleague's saved search is visible to the whole team and builds a workflow around \"the hero images search,\" only to find it doesn't exist for anyone else \u2014 because most DAMs default saved searches to private and require an explicit share or promotion to a shared collection.","deep_link":""},"silo":[24],"class_list":["post-2469","glossary","type-glossary","status-publish","hentry","silo-glossary"],"_links":{"self":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2469","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary"}],"about":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/types\/glossary"}],"version-history":[{"count":3,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2469\/revisions"}],"predecessor-version":[{"id":3469,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2469\/revisions\/3469"}],"wp:attachment":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/media?parent=2469"}],"wp:term":[{"taxonomy":"silo","embeddable":true,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/silo?post=2469"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}