The way most teams share design assets with marketing is a person: someone asks in Slack, a designer stops mid-flow, digs up the file, exports it, posts it. Twenty minutes later the requester has their banner — and three weeks later, someone else asks for the same one, because a Slack thread is where files go to be lost again. The loop feels like collaboration. It is actually a retrieval system with a human as the search engine, and it fails the moment that human is busy, on vacation, or gone.
TL;DR
- Every asset request interrupts a designer and produces a copy that immediately starts going stale.
- Marketing needs view-and-download access, not edit access — a role, not a favor.
- Hand off campaigns as curated collections, not file dumps.
- Agencies get a share link to a collection — no accounts, no zip files, revocable.
- Answer requests with the search that finds the asset. Two weeks of pedantry, then the requests stop.
01 — The problem
The request loop and what it costs
Tally a normal week: the logo in white, the pricing screenshot, the social card from the spring launch, “the illustration we used in that deck.” Each request costs a context-switch on the design side and a wait on the marketing side — and the hidden third cost is worse. Every fulfilled request creates an untracked copy: a file in a thread, on a desktop, in a presentation, that keeps circulating long after the asset is superseded.
That's how last year's logo ends up in this year's webinar. Not malice, not carelessness — just copies outliving their truth, because distribution happened person to person instead of from a source everyone can query.
02 — Access
Viewer access: the seat nobody buys
The reflex solution — invite marketing into the design tool — fails on both ends: design tools price by editor seat, and a working file is a workshop, not a shelf. Marketers don't want to navigate artboards; they want to type “pricing hero” and download.
The right shape is role-based access to the library itself. Four roles cover a small team: an owner and admins who govern, members who import and curate, and viewers — who search, preview, and download, and can't change anything. Viewer is the role most of the company should have. It turns “can you send me” into “I got it,” with zero risk to the catalogue's integrity.
03 — Handoff
Collections as the unit of handoff
Search serves the one-off need; campaigns need a package. The handoff unit is a curated collection — the campaign kit: every approved deliverable for the launch, in one place, maintained as finals land.
The kit inverts the request dynamic. Instead of marketing asking asset by asset, design publishes once: “the Q3 launch kit is live.” Executors pull what they need in the ratio they need. And when membership follows a rule — everything tagged with the campaign — a smart collection maintains itself: tag the new banner at import and it appears in the kit without anyone remembering to add it.
Two kits that pay rent forever
- The brand kit — logos in every lockup and background, color and type references. The answer to half of all requests.
- The sales set — the dozen visuals sales may drop into any deck, pre-approved so nobody has to ask.
05 — Behavior
Killing the Slack habit
Infrastructure without behavior change just moves the requests. The behavior fix costs two weeks of mild pedantry: when someone asks for an asset, answer with the library search that finds it — the link to the query, not the file. When someone asks for “everything for the launch,” answer with the kit.
It feels fussy exactly until it doesn't. People learn the front door because the front door is faster than asking, and the requests taper to the genuinely novel. The designer gets their flow back; marketing gets instant answers; the whole system earns its keep on interruptions alone.
06 — FAQ
Common questions
How do I share assets with an agency that has no account?
A public share link on a curated collection. The agency sees exactly that collection — current, downloadable, nothing else — and you retire the link when the engagement ends. No seat management, no zip files going stale in email threads.
Is a public share link safe for brand assets?
Treat it like any unlisted URL: anyone holding the link can view, so share it deliberately and revoke it when done. For most marketing deliverables that risk profile is fine — these assets are made to be published. Anything genuinely confidential belongs behind team membership, not a link.
What belongs in a campaign kit collection?
Every approved deliverable someone outside design needs to execute the campaign: banners in each ratio, social cards, email headers, the landing hero, logo lockups, and the copy-adjacent visuals. If marketing still has to ask for something mid-campaign, the kit was incomplete — add it and the kit is right next time.
How does marketing find assets without learning the taxonomy?
Search does the translating. Full-text covers titles and tags in plain words, and semantic search handles descriptions like "dark hero with the gradient" — no tag knowledge required. The taxonomy exists so filters work for the people who curate; everyone else just types what they remember.
In DesignVault this is the default shape: four roles with viewer access for the people who only retrieve, manual and smart collections for campaign kits that maintain themselves, and public share links on any collection — live, view-only, revocable. Search speaks English and French, so the person retrieving never needs the taxonomy lesson.