Pimcore Asset Experience Portal – Your Brand Media, Self-Service.

An Asset Experience Portal (AXP) is the second variant enabled by Pimcore's enterprise-only Portal Engine bundle (a sibling product to the Product Experience Portal, but with assets instead of product Data Objects as primary data). Target audiences are press, agencies, and dealers with media needs: they should be able to search image, video, and document holdings themselves and download them in the right resolution or conversion.

What Exactly Is an Asset Experience Portal?

An AXP builds on Pimcore as a Digital Asset Management (DAM) system: assets, metadata schemas, and thumbnail renditions already maintained in the system. Search facets in the portal come from Enterprise Asset Metadata and system attributes such as file type or creation date. The key difference from a simple file-sharing link: downloads run through format conversion: original, named thumbnail configurations, custom dimensions, or metadata exports can be selected directly in the portal, without your team having to handle every request manually.

Permissions Tuned to Your Data Model

Asset pool permissions are granted per workspace: view, download, edit, update, create (including upload with optional review routing), delete, manage subfolder, or restriction to "own assets only." A portal can combine asset and object pools, for example a brand portal that brings a media library and a product catalog together in one interface, details on the Product Experience Portal page.

Direct Edit as a Companion for Creative Workflows

For teams that want to edit assets directly in desktop applications, a Direct Edit bundle complements the portal: assets open directly in the local desktop app via a client agent, technically mediated through Mercure. That's not a replacement for the portal itself, but an addition for creative workflows where open-edit-save happens more often than pure browsing and downloading.

Technical Prerequisites

As with the Product Experience Portal: no AXP runs without the Generic Data Index backed by OpenSearch (2.7 or later) or Elasticsearch (8.0 or later). In multi-node operation, another often-overlooked requirement comes in: shared portal directories for cart-ZIP assembly, so download carts get assembled correctly across multiple server instances.

Governance for Legally Sound Media Distribution

Public share links with an expiration date and optional terms-of-use acceptance aren't a nice-to-have on an AXP, they're the difference between controlled and uncontrolled brand distribution. Anyone distributing press images or dealer-partner assets through time-limited, logged links instead of unlimited shares has defensible traceability in a dispute: an argument that regularly gets underestimated in brand-rights and compliance conversations.

Where an AXP Reaches Its Limits

An AXP doesn't replace a dedicated rights management or DRM solution with license tracking across contract terms. It's an access and distribution portal on top of your Pimcore DAM, not rights management in the legal sense. And as with the Product Experience Portal: portal permissions protect the portal interface, not automatically the raw asset URLs behind it: an additional webserver lock is still needed if assets shouldn't be directly reachable.

Why We Put Metadata Design Before Portal Configuration

A portal filters exclusively on indexed metadata. If the metadata schema only gets extended retroactively during portal configuration, duplicate work and inconsistencies pile up in the already-maintained asset base. That's why we bring DAM depth, metadata schema, thumbnail strategy, facet plan, and portal configuration together from the start, instead of treating them sequentially, the same way we approach every Enterprise Data & MDM project. This is the point where it becomes visible whether a portal project scales cleanly or needs constant rework after launch.