DAM for Agencies: How Collaboration with Brands and Clients Works
Agencies need up-to-date brand assets, and brands need their final campaign visuals back. A DAM provides the common ground for both. Find out which collaboration models exist, which features really help, and how to handle approvals, rights and handovers cleanly.
Andreas Werner

A new campaign is coming up. The agency needs product images, logos and existing ad visuals. The marketing team shares the files through various cloud folders and download links. During the design phase, it turns out that some images are outdated. Feedback arrives by email, and the revised version ends up in yet another folder. And shortly before the planned campaign launch, nobody is sure which visual was actually approved.
Situations like these cost time, on the agency side just as much as on the client side. It gets especially laborious when several agencies, internal teams and external service providers work on the same brand content.
Digital Asset Management (DAM) provides common ground for this collaboration. Images, videos, logos and other digital assets can be managed centrally, shared in a targeted way and organized across their entire lifecycle.
But how should agencies use a DAM? Does every agency need its own system, or does it make more sense for it to work directly in its client's DAM? And which features really make collaboration easier?
Why collaboration between agency and client often gets complicated
Agencies often look after several clients at once. For each of them, they create campaign visuals, social media graphics, videos, presentations and other marketing materials. At the same time, clients supply existing brand assets and product information that feed into new content.
Without a shared structure, the material quickly spreads across different systems and communication channels.
- The right file is hard to find. A product image sits in a cloud folder, the current logo in an email attachment and the latest campaign version on the agency's server. Anyone who needs a particular file often has to ask the person in charge first.
- Versions are hard to tell apart. File names like "Campaign_final_v3_new" are of little help when further changes are being made in parallel. In the worst case, the agency keeps working with an old template or marketing publishes an outdated version.
- Feedback and approvals are scattered. Corrections come by email, comments sit in presentations and important decisions are made in meetings. Later on, it is hard to trace which change was agreed or who approved a visual.
- Usage rights remain unclear. Not every image may be used indefinitely or on every channel. If information on licenses and permitted use is missing, it has to be checked again for every new use.
- Final assets stay with the agency. This often only becomes apparent after the project is over. If the brand wants to reuse them for a later campaign or hand them over to another service provider, the search starts all over again.
A DAM can reduce these problems. What matters, though, is not only the software but also how agency and client organize the management and use of their assets.
Who owns the DAM? Two models for collaboration
There are basically two options: the agency runs its own DAM and manages its clients' content in it. Or the client provides a DAM that the agency accesses with the appropriate permissions.
Both models can work. Which one makes more sense depends, among other things, on existing processes, the number of people involved and the responsibilities.
Model 1: The agency manages brand assets in its own DAM
An agency that looks after many clients and campaigns can organize its projects in its own DAM. That is where it stores briefing material, image files, videos, drafts and final campaign assets.
The advantage: the agency can standardize its internal processes and work in a uniform system environment. Creative teams don't have to learn a different filing structure for every client.
For this to work, the DAM must be able to keep different clients and projects cleanly separated. Roles and permissions should ensure that employees and external parties only access the content intended for them.
Collaboration with the client also needs to be defined. Are drafts provided for review directly in the DAM? How does the brand receive its final files? And who makes sure that updated logos or product images are replaced in the agency's storage?
The biggest challenge lies in the handover and long-term availability of the assets. If only the agency manages the complete media library, the client can become dependent on the agency's processes.
What should therefore be settled as early as the commissioning stage is covered further down in the section on asset ownership.
Model 2: The agency works in the client's DAM
In the second model, the brand or company runs the central DAM. External agencies get access to the content they need, matched to their tasks.
This approach is particularly interesting for manufacturers and retailers. They often manage large volumes of product images, logos, videos, data sheets and campaign materials. This content is needed not just by one agency but also by marketing, sales, e-commerce and other external partners.
When the agency works with the client's DAM, it accesses the centrally maintained asset library. Updated product images or new brand guidelines can be provided where other stakeholders will find them too.
A suitable roles-and-permissions concept controls which content an agency may view, download, add to or edit. Ideally, corrections and approvals can also be built into the shared processes.
For the brand, this brings several advantages:
- It keeps track of its central media library.
- Agencies can work with up-to-date, approved brand assets.
- Final campaign content can be secured within the company for the long term.
- Other departments and service providers can reuse existing assets.
- If the agency changes, the media library remains available in the client's system.
However, this model needs clear processes. The agency has to know where to find relevant content, how to deliver new assets and who on the client side is responsible for approvals.
The DAM should also support creative work rather than create extra detours. Interfaces to existing creative tools can help here.
And what if both sides use their own systems?
A company doesn't always have to choose one of the two models.
In practice, a hybrid approach can also make sense: the agency organizes its ongoing production in its familiar working environment. The client provides the binding brand and product assets through its DAM.
After production, the reviewed, final campaign content is transferred to the client's DAM in a structured way.
This way, both sides keep their proven ways of working. What matters is a clearly defined handover process, so that no outdated or incomplete files end up in the central media library.
So what matters is less who runs the DAM than where the binding assets are managed and how both sides access them.
What requirements must a DAM meet for agency work?
A DAM for collaboration between brand and agency has to do more than simply store files. It should support the entire handling of digital assets, from provision to later reuse. The asset management of a PIM system is usually not enough for this: it is geared to product data, not to approvals, usage rights and collaboration with external partners.
Clearly define access rights and roles
Not everyone involved needs access to all content.
An external design agency should, for example, be able to download product images and brand logos. Perhaps it may also upload new drafts. Approval for publication, on the other hand, stays with the client's marketing team.
A suitable DAM lets you map such responsibilities through roles and permissions. Clearly separating access is especially important when several agencies or brands are involved.
It should also be clear what happens after the project ends. When access is no longer needed, the corresponding permissions should be adjustable or revocable. Time-limited shares, such as download links with an expiry date, are also useful.
Keep track of versions, feedback and approvals
Correction loops are part of creative work. They only become a problem when different versions and pieces of feedback are circulating in parallel.
Versioning helps manage an asset's revisions in a traceable way. It shows which version is current and how a visual has changed over the course of the project.
Collaboration gets even better when feedback can be linked directly to the asset in question. Instead of spreading feedback across several emails, everyone refers to one specific file. Annotations are especially handy, letting you place a comment directly on a specific area of an image.
Defined approval statuses add further clarity: a visual is, for example, still in progress, awaiting review or already approved for certain channels.
This makes the DAM a reliable basis for media approval without it having to take over every task of a project management system.
Find assets quickly and use them safely
A DAM is of little use if employees still have to spend a long time searching for the right files.
That is why meaningful metadata and good search functions matter. Product numbers, campaign names, image types, brands or intended uses help find relevant assets in a targeted way.
Information on usage rights should also be stored directly on the asset wherever possible.
An example: an agency is developing a new social media campaign and wants to reuse an existing testimonial photo. In the DAM, the stored information shows for which period, which countries and which media channels the visual was licensed.
This cuts down on queries and supports responsible handling of protected content. The system does not, however, replace checking the actual usage rights.
A new question is AI-generated content: if an agency delivers visuals that were created or edited with AI, this should be documented on the asset. We explain the role standards such as C2PA play in this in our article C2PA in DAM, and the legal background in our article AI images and copyright.
AI features can make searching easier, too. Automatic tagging, AI search in natural language or visual similarity and object search help especially with large image libraries where not every visual has been described manually.
Deliver content for different channels
A finished campaign rarely consists of just one file format.
The key visual may be needed as a high-resolution print file, while the online shop uses an optimized web version. Social media adds further aspect ratios and formats.
A DAM should therefore be able to generate the required variants from an approved master asset instead of maintaining a separate copy for each channel. Modern systems do this automatically and, if needed, in real time. Being able to distribute approved content in a targeted way is just as important.
Integrations with creative software such as Adobe Photoshop, Illustrator and InDesign or Figma and Canva can also be useful. They connect central asset management more closely with the creative teams' tools.
From briefing to finished campaign: how a DAM workflow works
The following example shows what collaboration can look like in practice.
A manufacturer is launching a new product line. An external creative agency develops campaign visuals for it, which will later be used in the online shop, on social media and in printed advertising materials.
1. The brand provides the source material
At the start, the agency gets access to the product images, logos, brand guidelines and existing ad visuals it needs.
Instead of gathering the files one by one, the marketing team can provide the relevant content in the DAM. Thanks to structured tagging, the agency also finds additional visuals it can use for the design.
Existing project management or communication tools can still be used for the actual campaign briefing.
2. The agency develops new campaign assets
Based on the material provided, the agency creates various drafts.
These include, for example, a key visual, banners for the online shop and visuals for social media. The creative work still takes place in the graphics and design programs intended for it.
Depending on the agreed working model, new files are then stored in the client's DAM or initially in the agency's environment.
What matters is that the individual revisions remain traceable.
3. Marketing and agency align on the drafts
The marketing team reviews the visuals for brand impact, product claims and design requirements.
If changes are needed, the feedback should be assigned as clearly as possible to the asset in question and its version.
That way, everyone knows which version a comment refers to. The agency can make corrections precisely without having to go through older rounds of feedback again.
4. The final visuals are approved
After the corrections, the company reviews the finished campaign assets. Depending on internal processes, several departments may be involved, such as marketing, product management or legal.
Once the content has been reviewed, it receives the corresponding approval status.
5. The assets are delivered to the individual channels
After approval, the e-commerce team needs the campaign images for the online shop. The social media team uses suitable formats for its posts, and the print shop receives the required high-resolution files.
A DAM can support the controlled provision and distribution of these different media versions – ideally without the agency having to create and upload each format individually.
The advantage of this process is not that as many work steps as possible move into a single piece of software. Rather, agency and client always know which assets are available, in progress or approved for publication. Here, the DAM is the leading system.
After the campaign: why asset ownership still matters
Work with the assets created does not end with the campaign launch.
Six months later, sales may need a campaign visual for a presentation. The e-commerce team wants to reuse a product image for a seasonal promotion. Or a second agency is to adapt the existing materials for another market.
If the final files are only stored in the original agency's storage, coordination and search effort arises all over again.
That is why it should be settled as early as the commissioning stage which assets will be handed over to the company after the project ends. Besides exported images and videos, this can include open layout files, relevant metadata and information on usage rights.
Which files and rights actually have to be handed over depends on the contractual agreements. Storing them centrally in the DAM does not by itself grant any additional usage rights.
For manufacturers and retailers, a well-maintained long-term asset library is particularly valuable. They can use existing content in further campaigns, markets and sales channels, provided the respective rights allow it.
A later change of agency also becomes easier. The new agency can access the existing, approved asset library without having to request all materials again from the previous service provider.
Checklist: what brands and agencies should look for in a DAM
Whether a DAM really makes collaboration easier shows in day-to-day workflows. When choosing a system, practical questions are therefore the most helpful.
- Central access: Can internal teams and external agencies easily find the assets they need?
- Roles and permissions: Can access be controlled specifically for different projects, brands and stakeholders?
- Versioning: Are changes and earlier revisions traceable?
- Feedback and approvals: Can review steps and approval statuses be built into the asset process in a meaningful way?
- Search and metadata: Can content be found by product, campaign, category and other attributes?
- Usage rights: Can relevant license information and time restrictions be documented on the asset?
- AI support: Do AI features help with search and tagging, and can AI-generated content be labeled as such?
- Formats and integrations: Does the system support existing creative tools and automatically generate the required media formats from a master asset?
- Handover and reuse: Do final files remain available after the campaign ends, and can they be passed on in a controlled way?
Not every organization needs the same features. What matters is which tasks the DAM is meant to take on in the interplay between brand, internal teams and external service providers.
How TESSA supports collaboration with external agencies
With TESSA, you as a manufacturer or retailer manage product images, logos, videos, documents and campaign visuals centrally and provide them to internal and external stakeholders. As an AI-native DAM for e-commerce, TESSA is designed so that marketing, e-commerce and agencies can work independently of one another – on the same data.
Several features are particularly relevant when working with agencies.
Roles and permissions control access at a granular level, down to individual folders. This lets you share exactly the campaign folder an agency needs for its assignment. With visibility settings, you also decide whether an asset is available only internally or externally as well – optionally time-controlled with a start and end date, for example for visuals that should only become visible at campaign launch.
Versioning also supports working on files together. Changes to assets remain traceable, and earlier revisions can be restored if needed.
For usage rights, you store a license expiry date on the asset, optionally per version. If a license is about to expire, TESSA can notify you in advance. That way, nobody accidentally uses a visual whose rights have expired.
With TESSA Workflows, you can also organize processes for delivering, reviewing and approving media. A comment can be added with every status change, and annotations let you mark requested corrections directly in the image. The exact scope of features depends on the TESSA edition used and its configuration.
For creative teams, there are connectors for Photoshop, InDesign and Illustrator. Agencies use them to search, open and edit assets directly in the Adobe application and save them back to TESSA as a new version. Creative tools such as Figma and Canva can be connected as well.
Transformations save rounds of coordination around formats: from an approved master asset, TESSA generates variants on the fly – cut out, scaled or converted. Every asset gets its own URL, whose parameters let the online shop or website fetch the right size in real time. So the agency delivers one final visual instead of numerous format variants.
With TESSA Drive, you work with assets as directly as in a familiar file system. This lowers the barrier to entry for agencies that have been working with folder structures and makes the hybrid approach easier.
If external partners mainly need access to approved brand materials, TESSA BrandHub is another option. The brand portal lets you provide selected images, videos, documents and product information. Permissions can control access to views and downloads, among other things.
AI search helps you find suitable visuals: you find images by describing them in natural language, through similarity search or by marking an object in an image and searching for comparable visuals – even without manual tagging. Via the native MCP server, AI assistants such as Claude or ChatGPT can also be connected directly to TESSA.
This allows brand companies to build a central media library and involve their agencies in content processes in a targeted way. Which access and working models can be implemented in practice should be assessed against the respective requirements.
About the author

Andreas Werner
DAM & PIM Consultant
For over 25 years, our data uncle has been helping companies increase their sales with the help of product data. The passionate wanderer is on fire for DAM and PIM.


