Repository Browser access fails on publish or preview instances

Last update: July 10, 2026

Access to the Repository Browser for Publish or Preview tiers in the AEM Developer Console fails because required Adobe Admin Console product profiles or Cloud Manager access are missing or configured incorrectly. Assign the correct product profiles for the appropriate Publish or Preview environment and ensure the user has the Developer - cloud service role to restore access.

Description description

Environment

AEM as a Cloud Service (AEMaaCS)
AEM Assets Essentials

Issue/Symptoms

Repository Browser returns a 403 Forbidden error on publish or preview instances.
Repository Browser is missing from the Developer Console.
Publish or preview instances do not appear in the instance dropdown.
Access works on some instance types but not others.

Cause

The required access profiles are not assigned for the specific publish or preview environment. In some cases, the required developer role is not assigned, preventing preview instances from appearing in the Developer Console and blocking repository access.

Resolution resolution

To resolve this issue, follow these steps:

Open the Admin Console and review the access profiles assigned to the affected environment.
Ensure the user is assigned to the required publish or preview access profile.
If the preview instance is missing, verify that the required developer role is assigned.
Sign out of all Adobe experience Cloud sessions, then back in to refresh permissions.
Return to the Developer Console and verify that the Repository Browser loads successfully.
Review application logs, instead of this review AEM error logs for repository browser exceptions.

recommendation-more-help

experience-cloud-kcs-help-kbarticles