DocumentationExperience Cloud KCS

AEM solution for Publish Repository Browser access to /conf and related folders

Last update: July 21, 2026

If the Publish Repository Browser does not show /conf or similar folders, the content usually still exists but the current account lacks the required Publish-side access. Review the assigned Cloud Manager and AEM product profiles, then retest the affected Publish instance to restore visibility where that access is supported.

Description description

Environment

Adobe Experience Manager as a Cloud Service

Issue/Symptoms

  • The Publish Repository Browser shows empty or missing paths such as /conf, /home, or /var.
  • Paths that are visible on Author are not visible on Publish for the same environment, or they appear in one environment but not another for the same user.
  • Some code-managed or immutable areas, such as client libraries, i18n resources under /apps, or OSGi configurations, may not appear on Publish in the same way as mutable repository content.
  • You can confirm the issue safely by comparing the same path in the Repository Browser on Author and on the affected Publish instance. If the path exists on Author but is not visible on Publish, review the assigned access roles and product profiles for that environment.

Resolution resolution

Try the following steps to solve the issue:

  1. Open the Repository Browser for the Author service and confirm that the missing path, such as /conf/<site> or /home, exists there. If the path is also missing on Author, the issue is not limited to Publish visibility and you should review the repository content itself.
  2. Check whether the path is expected to be visible on Publish. Some immutable or code-managed areas, such as client libraries, i18n resources under /apps, and OSGi configurations, may not appear in the Publish Repository Browser in the same way as mutable content.
  3. In Adobe Admin Console, verify that the affected user has the correct access for the target environment. Repository Browser access requires the appropriate Cloud Manager and AEM product profiles, and full Publish visibility requires a Publish administrator-level profile for that environment.
  4. If the required profile is missing, add the user to the correct Publish profile, and apply the equivalent Preview profile if you need the same access on Preview. If your organization maps product profiles to AEM groups, confirm that the synchronized group is available and has the expected effective permissions.
  5. Allow time for permissions to synchronize, then sign out and sign back in before reopening the Developer Console and Repository Browser. Reauthentication helps refresh the latest Cloud Manager and AEM permissions.
  6. Retest the specific Publish instance and compare the results with Author. The expected result is that supported paths such as /conf, /home, or /var become visible when the correct access is in place.

If the following symptoms occur and the troubleshooting steps produce the following results, submit a ticket to Adobe Support.

  • The path is visible on Author but still missing on Publish after the correct environment-specific access profiles are assigned and synchronized.
  • The issue affects only one environment while the same user and permissions work as expected in another environment.
  • The Repository Browser continues to fail to load, returns access errors, or the expected Publish or Preview instance does not appear after you refresh access.

Contact Adobe Support.

recommendation-more-help
experience-cloud-kcs-help-kbarticles