AEM asset sharing with Brand Portal: setup and workflows
AEM Brand Portal gives marketing teams a controlled way to distribute approved digital assets beyond the core Adobe Experience Manager environment. Images, video, documents, logos and campaign files can be organised centrally in AEM Assets, then shared with agencies, franchisees, retailers and regional teams without giving every contributor access to the authoring environment.
For Australian organisations, the value is especially clear when teams are spread across Sydney, Melbourne, Brisbane and Perth. A well-designed setup reduces duplicate downloads, limits outdated campaign material and creates a repeatable path from asset creation to external delivery. The strongest results come from treating Brand Portal as part of an operating model, rather than as a separate file library.
Start with a clear asset model
Begin by deciding which assets belong in AEM Assets and which audiences need Brand Portal access. Product photography, approved social crops, television commercials, point-of-sale artwork, brand guidelines and translated campaign files are common candidates. Working files, drafts and confidential material should remain restricted to internal authors and reviewers.
A useful folder structure often follows market, brand, campaign, product category and asset type. Avoid creating a deep hierarchy that forces users through many clicks. Collections can provide a more flexible view for seasonal campaigns or audiences such as retail partners, field sales teams and media agencies.
Metadata is more valuable than folders when users need to search at scale. Define fields for product code, market, language, usage rights, campaign dates, approval status and accessibility information. Australian retailers may need separate variations for local promotions, while a national organisation might need assets tagged for New South Wales or Victoria. Clear naming rules make automation and reporting easier later.
Configure the publishing path
Brand Portal depends on a reliable connection between the AEM author environment and the external portal. Confirm the relevant integration, user provisioning method, replication or publishing agents, network rules and Adobe identity configuration before loading a large asset library. Test with a small set of representative files, including a large video, a layered design file and several image formats.
Renditions should be planned before distribution begins. A single original image may need web, mobile, print and social-media variants, with different dimensions, quality settings and file formats. Adobe’s processing profiles provide a practical basis for defining those transformations consistently instead of asking users to resize files manually.
Check the complete path from upload to availability. A test should verify metadata extraction, thumbnail generation, rendition creation, publication, search indexing and download permissions. It should also confirm how updates behave: if an approved image is replaced, users should be able to distinguish the current version from an older download.
Build practical approval workflows
A useful workflow separates creative production from business approval. For example, a photographer or designer can upload an asset, a brand manager can review its visual quality, a legal or compliance reviewer can check claims and rights, and a channel owner can approve its release. Each step needs an owner, a status and a clear exception path.
Workflow rules should reflect asset risk. A low-risk internal presentation template may need one approval, while a pharmaceutical advertisement or financial-services campaign may require legal review, expiry dates and evidence of consent. Avoid sending every file through the longest process, as unnecessary controls encourage teams to bypass the platform.
Regional content needs additional care. An Australian campaign may require an English master plus versions for other markets, and translated assets should remain linked to the source where possible. AEM teams can use a language copy workflow to coordinate copies, translation tasks and review states without losing the relationship between the original and its variants.
Govern access, metadata and rights
Brand Portal users should be assigned access according to their business role, not simply their organisation. An agency working on a summer campaign may need access to one collection for three months, while a national distributor may require ongoing access to approved product assets. Group-based permissions are easier to audit and revoke than individual exceptions.
Rights metadata must be treated as operational information. Record photographer permissions, model releases, music licences, territory restrictions and end dates where relevant. A portal user downloading an image should be able to understand whether it can be used in paid advertising, organic social content, packaging or internal communications.
Privacy obligations also matter. Under Australia’s Privacy Act and the Australian Privacy Principles, personal information in campaign imagery must be handled carefully. A library containing customer photographs, employee profiles or event attendees needs appropriate consent, retention and access controls. Organisations should also consider whether data flows and support arrangements align with their internal requirements for Australian data handling.
| Capability | AEM Assets | Brand Portal | External file service |
|---|---|---|---|
| Primary purpose | Create, manage and approve master assets | Distribute approved assets to external users | Exchange files or collaborate broadly |
| Metadata control | Deep schemas, workflows and automation | Search and filtering based on published metadata | Often limited or inconsistent |
| Version confidence | Strong source-of-truth control | Publishes selected, approved versions | Depends on folder discipline |
| User access | Authors, reviewers and administrators | Agencies, partners and regional teams | Broad sharing with variable governance |
| Renditions | Automated image and media processing | Delivers prepared variants | Usually manual or application-dependent |
| Best governance use | Production and lifecycle management | Controlled self-service distribution | Short-term transfer or informal collaboration |
Operate sharing at Australian scale
A publishing process should include notifications, escalation and failure handling. If a reviewer does not act within two business days, the workflow can notify a team lead; if a licence is close to expiry, the asset owner can receive a warning. Practical email escalation patterns help turn stalled tasks into visible operational events.
Schedule releases around local business realities. A campaign approved late on a Friday in Melbourne may need to be available to a Perth team before its Monday morning, while a retailer in Queensland may have a different promotional deadline. Use explicit time zones, dates and release windows rather than relying on informal messages in email or chat.
Performance also deserves attention. Australian users may access large files from offices, stores or regional locations with uneven network conditions. Provide appropriately sized renditions, avoid forcing partners to download originals and monitor failed downloads. Mobile-friendly previews are useful for field teams checking assets while travelling between stores, although final production files should still be downloaded through controlled access.
Make adoption measurable
A Brand Portal implementation succeeds when users can find the right file quickly and trust that it is approved. Track search terms with no results, frequently downloaded assets, abandoned tasks, expired files, failed publishing jobs and inactive accounts. These measures reveal where metadata, folder structures or training need adjustment.
A short operating guide should explain how to request access, search by metadata, select a collection, check usage rights and report an incorrect asset. Training should use real campaign examples rather than generic software demonstrations. For teams in Sydney or Melbourne, live sessions may work well; distributed organisations can provide recorded demonstrations and concise process cards for regional users.
Use the following practices to keep the service reliable:
- Define one accountable owner for the asset taxonomy and metadata schema.
- Publish only approved assets to external collections, with visible expiry and usage information.
- Automate standard renditions for web, mobile, social and print requirements.
- Review external users and group memberships at regular campaign or quarterly intervals.
- Measure search success, workflow turnaround, downloads and expired-content incidents.
The operating model should be reviewed after each major campaign. Remove obsolete collections, update metadata values, examine recurring approval delays and confirm that permissions still match current partner relationships. This maintenance prevents Brand Portal from becoming another unmanaged archive.
AEM Asset Sharing with Brand Portal is most effective when technical configuration, content governance and human workflow are designed together. Start with a small collection, test the full publishing path, establish ownership and expand only after users can reliably locate, understand and download the correct asset. Explore the CIRCUIT session resources to deepen your AEM implementation knowledge, then apply the model to a controlled Australian campaign with measurable approval and distribution goals.