AEM Content Hub: Non-admin users unable to view assets despite correct permissions
This article addresses an issue where users with Content Hub user permissions can’t view assets in Adobe Experience Manager, while admin users can.
Description description
Environment
Adobe Experience Manager (AEM) Content Hub (all versions)
Issue/Symptoms
Users assigned to the Content Hub user profile are unable to view any assets in the Content Hub interface. When these users attempt to search or browse, no assets are displayed. Only users with admin profiles are able to see uploaded assets.
- No error messages are shown to affected users; the asset list simply appears empty.
- Issue isn’t reproducible for admin users.
- The problem may be related to users accessing the development repository instead of the production repository, where assets are actually available.
- Assignments in the Admin Console appear correct, and there’s no clear entitlement difference between working and non-working users.
Resolution resolution
-
Confirm with affected users which Content Hub repository they’re accessing:
- Ask users to open Content Hub using the production URL provided by the administrator or support team.
- Example production URL format:
https://experience.adobe.com/?repoId=#/@/assets/contenthub
-
If users are accessing a development repository, instruct them to switch to the production repository using the correct URL.
-
If users don’t require access to the development repository, revoke their access to it in the Admin Console. This ensures that the production repository is selected by default.
-
Have users log out and log back in to ensure repository selection changes take effect.
-
Verify that users with Content Hub user permissions can now view assets in the production repository.
Cause
The issue occurs when users access the development repository, which doesn’t contain the expected assets, instead of the production repository where assets are available. Repository selection mismatch leads to the appearance of missing assets for non-admin users.
Another potential cause is ABAC rules setup might prevent the users in question from being able to see the assets.