Adobe Experience Cloud
Content Hub uploads need a findable Assets handoff
Give directly uploaded Content Hub assets ownership, metadata, and review after they appear in Assets.
October 31, 2026
Direct upload is convenient for a contributor, but someone still owns the asset after it reaches the library. In an Adobe Experience League discussion, a team says uploads appear in new Hydrated-assets folders in AEM Assets with names that are hard to navigate. The accepted community answer suggests moving the asset to a clearer location, reviewing it, and then setting its approval status. The poster still wants a more systematic folder structure.
Treat upload as intake
Adobe's Content Hub upload guidance says assets display at the top level in Content Hub regardless of their source folder hierarchy, and emphasizes campaign, keyword, channel, and other metadata for discovery. That makes the upload form and metadata policy more important than a folder-only navigation plan. Define required campaign, owner, usage rights, region, and review status before inviting broad uploads.
Separate discovery from approval
Do not assume that an asset's presence in Content Hub means its downstream use is governed. Adobe's approval guidance describes approval status as the control for availability. For a sample upload, trace where it appears in Assets, what metadata survives, who can edit it, and which review step changes its status. Record the exact behavior in your tenant rather than treating a community folder name as a universal path.
Assign a post-upload owner
Give one operations role responsibility for reconciling new uploads with the canonical asset library. Decide when to move assets, when to leave the generated location alone, and how to retain stable references if assets are relocated. Test search by campaign and keyword before rebuilding a folder taxonomy. A short weekly exception list is more useful than a large unowned intake queue.
Adovo’s view
Easy intake creates value only when retrieval and approval stay easy. Folders are a storage decision; metadata and ownership are the operating system. Design the handoff before the library becomes a warehouse of anonymous files.