Short answer
The brand manager in a DAM selection owns the brand portal, guideline control and regional consistency. The brand manager leads the brand portal and regional adaptation scenarios at Checkpoint 5: Test and scores the brand portal and sharing criterion. The role matters most when agencies, regions or partners download assets, typically from the first external user onwards.
What the brand manager owns in a DAM selection
The brand manager owns three outcomes in a DAM selection: one portal for approved assets, guidelines next to the assets they govern, and regional adaptation that keeps the brand intact.
Brand portal
A brand portal is a branded, permission-controlled area of a DAM where internal and external users find approved assets and guidelines. The brand manager defines who uses the portal, what each group sees and how agencies get access. The brand portal glossary entry covers the term.
Guideline control
The brand manager owns the link between guidelines and assets. Logos, colour values, typography and templates stay current in one place. When a guideline changes, the outdated assets leave circulation on the same day.
Regional consistency
The brand manager owns how regions and markets adapt global assets. Local teams need templates with locked brand elements, translated metadata and a clear approval path. The selection tests all three on real regional cases.
Usage rights for brand assets
The brand manager shares rights ownership with the DAM manager for campaign imagery, talent and stock. Usage rights are the licence terms that define the channels, regions, periods and purposes for which an asset may be used. The brand manager confirms that expired assets disappear from the portal and from shared links.
Checkpoints the brand manager leads
The brand manager supports Checkpoints 1 and 2, leads two scenarios at Checkpoint 5 and scores two criteria at Checkpoint 6.
| Checkpoint | Brand manager role | Output |
|---|---|---|
| 1 Map | Support | Inventory of brand assets, agencies, regions and portal users |
| 2 Define | Support | Portal and regional user stories with priorities |
| 3 Justify | Contributor | Measured baseline for asset requests handled by email |
| 4 Shortlist | Reviewer | Check of external user pricing per vendor |
| 5 Test | Scenario lead | Brand portal and regional adaptation scenarios |
| 6 Score | Scorer | Scores for brand portal and sharing, and rights and licence management |
| 7 Sign | Reviewer | Confirmation that external user terms match the portal plan |
The brand manager writes the portal user stories in Checkpoint 2. Each story names the user group, the task and the measure of success, such as "an agency designer downloads the approved logo set in the right format within two minutes".
Demo requests the brand manager makes
The brand manager asks vendors to run portal and regional scenarios on the buyer's own assets and guidelines. DAMSelection assessment: generic vendor demos carry no selection value, so each request in this list belongs in the scripted demo.
- Show an agency user receiving access, downloading approved assets and losing access on a set end date.
- Show a regional marketer finding the approved logo lockup for one market within three filters.
- Show a guideline page that links to the live assets, and the update when a logo version changes.
- Show an expired campaign image disappearing from the portal, collections and existing share links.
- Show a template where a region edits the headline and image while logo, colours and layout stay locked.
- Show automatic conversion of a master image into the social, web and print renditions the guidelines specify.
- Show download reporting per region, agency and asset.
- Show the price for 50, 200 and 500 external portal users.
The brand manager scores what a non-specialist user experiences. A portal that needs training for agencies fails the scenario, whatever the admin features.
Documents the brand manager uses
The brand manager works from four documents during the selection.
| Document | Purpose | DAMSelection resource |
|---|---|---|
| Brand guidelines | Source of rules the portal must enforce | Internal document |
| Portal user stories | Requirements per user group | User stories guide |
| Rights inventory for campaign assets | Basis for expiry and region rules | Rights management guide |
| Rights exposure estimate | Size of the risk from expired or unlicensed use | Rights Exposure Estimator |
The rights exposure estimate feeds the business case. The brand manager hands it to the CMO in Checkpoint 3.
Risks the brand manager catches
The brand manager catches five risks that other seats rarely test.
- Rogue copies: agencies and regions keep local copies when the portal is slow or hard to search. The brand manager tests search with external users.
- Expired rights in circulation: share links and downloaded copies outlive the licence. The brand manager tests expiry across portal, collections and links.
- External user pricing: per-seat pricing for agencies and partners can multiply cost. The brand manager checks the definition of a user in every quote.
- Guideline drift: guidelines stored outside the DAM fall out of step with the assets. The brand manager tests guideline pages linked to live assets.
- Regional workarounds: regions without editable templates rebuild assets in other tools. The brand manager tests local adaptation with locked brand elements on real regional cases.
The brand manager shares the external user pricing finding with procurement. Procurement then negotiates portal tiers before signature.
Worked example: external user cost
External portal users can move a DAM quote more than internal seats. The figures in this worked example are hypothetical.
A brand runs 40 internal users and works with 12 agencies and 30 regional partners. The brand manager counts 180 external people who download assets at least once a quarter.
| Pricing model | What gets counted | Users priced |
|---|---|---|
| Per seat, external users included | Every named user | 220 |
| Per seat, portal users free | Internal users only | 40 |
| Platform tier with portal module | Internal users plus a portal add-on | 40 plus one module |
The same portal plan can price 40 or 220 users depending on the model. The brand manager brings this count to Checkpoint 4, so the shortlist filters on realistic volumes. The DAM pricing guide explains the three pricing archetypes.
How the brand manager works with the other seats
The brand manager depends on the DAM manager for metadata and on procurement for external user terms, as set out in the DAM selection roles overview.
- With the DAM manager: agree the brand, campaign, region and rights fields in the metadata schema.
- With the CMO: supply adoption scores and the rights exposure estimate.
- With procurement and legal: confirm external user definitions, portal tiers and agency access terms.
- With creative operations: confirm how designers place approved assets in creative tools such as Adobe Creative Cloud and Figma.
What the brand manager measures after go-live
The brand manager measures three portal outcomes after go-live and compares them with the Checkpoint 3 baseline.
| Measure | Baseline source | Review frequency |
|---|---|---|
| Asset requests handled by email | Brand team inbox count over four weeks before selection | Monthly for the first six months |
| Share of downloads by external users | Portal download report | Quarterly |
| Assets used after licence expiry | Rights audit sample | Quarterly |
The email request count shows whether the portal replaced manual work. The external download share shows whether agencies and partners adopted the portal. The expiry sample shows whether rights rules work in practice. The brand manager reports all three to the CMO, who checks them against the business case before renewal. The DAM KPIs guide explains how to set each baseline.
Brand manager checklist
The brand manager checklist covers eight steps before scoring closes.
- List every external user group with counts and download frequency.
- Write portal and regional user stories with measurable outcomes.
- Add brand assets to the demo sample set, including expired and regional variants.
- Script the portal, expiry and regional adaptation scenarios.
- Recruit one agency user and one regional marketer as demo testers.
- Score portal and rights scenarios against published pass criteria.
- Check the external user definition in every quote.
- Hand the rights exposure estimate and portal scores to the CMO.
Frequently asked
What does a brand manager need from a DAM?
A brand manager needs a DAM with a permission-controlled brand portal, guidelines linked to live assets, rights expiry that removes assets everywhere, and templates for regional adaptation with locked brand elements. Download reporting per region and agency shows whether the portal replaces email requests.
Does a brand manager need a separate brand portal tool?
A brand manager needs a separate brand portal tool only when the shortlisted DAM lacks portal permissions, guideline pages or external user pricing that fits the plan. Most DAM segments include a portal, and the brand portal scenario at Checkpoint 5 shows whether the built-in portal meets the user stories.
How do you keep regional teams on brand with a DAM?
Regional teams stay on brand when the DAM offers templates with locked logo, colour and layout elements, translated metadata and a regional approval path. The brand manager tests these on real regional cases during the demo, with one regional marketer as tester.
Who approves assets in a DAM workflow?
The brand manager or a delegated brand reviewer approves brand-critical assets in a DAM workflow, and legal approves claims or regulated content. The selection team agrees the approval steps in Checkpoint 2 and tests them in the workflow scenario.
How many external users does a brand portal need?
A brand portal needs as many external users as the agencies, partners and regional teams that download assets each quarter. The brand manager counts them in Checkpoint 1, because external user volume often changes the pricing archetype that fits best.