Provision Content Hub for multiple programs in the same AEM organization

Last update: June 27, 2026

Content Hub provisioning for multiple programs within the same Adobe organization results in identical organization segments in URLs, which cannot be modified. This limitation makes it difficult to distinguish between program-specific Content Hub instances. To resolve the issue, configure branding and distinguish instances using labels.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS)

Issue/Symptoms

A newly provisioned Content Hub for an additional program in the same AEM as a Cloud Service organization displays a URL that uses the same organization identifier (the segment after @) as an existing program.
The organization segment in the Content Hub URL for the new program cannot be modified or changed.
Only the production Content Hub environment is provisioned, and no dev or stage environments are available when the setup does not include an Assets Ultimate contract.
Similar Content Hub URLs across multiple programs create confusion when identifying and accessing the correct instance.
No error message appears during provisioning; the behavior reflects expected configuration constraints.

Root cause

Content Hub URLs are defined at the Adobe organization level, so all programs share the same organization identifier. Differentiation across programs relies on branding and repository configurations, not URL changes.

Resolution resolution

Follow these steps to distinguish and manage Content Hub instances across multiple programs within the same Adobe organization:

Review the official documentation for deploying Content Hub to understand provisioning constraints within a single Adobe organization.
Differentiate Content Hub instances for each program by creating clearly labeled bookmarks, such as “Program A Content Hub” and “Program B Content Hub,” that point to their respective URLs.
Configure distinct branding for each Content Hub instance by navigating to Content Hub configuration > Branding, and then set unique logos, banner text, and other visual identifiers to distinguish each program. Refer to Configuring Content Hub UI Options for guidance.
Verify contract entitlements and note that preproduction environments (development and stage) are available only when the setup includes an Assets Ultimate contract; otherwise, only the production environment is provisioned.

recommendation-more-help

experience-cloud-kcs-help-kbarticles