Content Hub share links do not complete the AEM asset edit handoff

A Content Hub user shares an asset link with a librarian and asks for an edit. The librarian opens the link but cannot jump directly to that same asset in AEM Assets. An Experience League conversation describes the resulting search-by-file-name chore and a possible custom extension. This is a handoff problem between the distribution experience and the editing system, not simply a search complaint.

Define what the request must identify

The requester should supply a stable asset identifier, the intended change, and a Content Hub link. File names can repeat or change; a URL that lands in a different application is not proof of identity. Test whether an existing asset ID, job number, or another unique property can be shown in Content Hub and searched in Assets view. Make the librarian confirm a match using metadata and rendition before editing.

Use configuration before custom development

Adobe’s Content Hub configuration guide documents metadata display, filters, and bulk search controls. Pilot a visible unique field with a handful of assets and a simple edit request template. Measure whether the librarian can find each original asset without relying on a fuzzy name match. The community author ultimately considered file-name bulk search as an interim path; its adequacy depends on naming discipline in that library.

Build a shortcut only with identity and access checks

If search remains too slow, scope a Content Hub UI extension that builds a link to the same asset in Assets view. The community discussion identifies this as development work, not a native button. Validate URL construction against moved assets, permissions, and environments. A shortcut that opens a similarly named but different asset can create a silent content error. Include an explicit not-found state rather than guessing.

Adovo’s view

The work is done in Assets, but the request begins in Content Hub. That boundary needs a stable identity. Give the librarian one unambiguous asset first; optimize the click path after identity and permissions are sound.