DocumentationExperience Cloud KCS

Troubleshoot asset visibility issues caused by ABAC rules in AEM Content Hub

Last update: October 26, 2026

Adobe Experience Manager as a Cloud Service (AEMaaCS) Content Hub may not display expected assets when Attribute-Based Access Control (ABAC) rules are incorrectly defined, imported, or applied, or when automation introduces rule errors. To resolve the issue, review the ABAC rules and metadata mappings, correct conflicting or incorrect rules, and validate asset visibility for affected groups.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS) Content Hub

Issue/Symptoms

  • Groups are unable to see the expected assets in the Content Hub UI.
  • Only assets with certain metadata values, such as contentAudience set to all, are visible, while other assets aren’t visible.
  • The Content Hub UI may appear empty for some groups.

Root cause

The issue typically occurs in non-production environments when ABAC rules are incorrectly defined, imported, or applied, or when automation tools introduce errors during rule application.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Review the ABAC rules configuration file for correct syntax and logic. Ensure that all intended groups and asset metadata attributes are properly defined.
  2. Review the mapping between groups and asset attributes, such as contentAudience or other relevant metadata properties. Verify that the values in the rules match the actual metadata values on the assets, including case sensitivity and spacing.
  3. If you use automated tools or scripts to apply ABAC rules, confirm that the rules are correctly imported and applied for all groups. If you find issues, manually update the ABAC rules to ensure that all groups have the correct access.
  4. Remove conflicting or duplicate ABAC rules for affected groups to prevent rule conflicts. Ensure that only one active rule per group exists for a given restriction.
  5. After updating the rules, sign in as a member of each affected group and validate asset visibility in the Content Hub UI. Confirm that assets with the appropriate metadata values are visible to the corresponding groups.
  6. Repeat the validation across all relevant environments to ensure consistency.
  7. If you use automation or bots to apply rules, monitor their behavior to ensure that they don’t introduce incorrect rules. Address any automation issues as needed.
recommendation-more-help
experience-cloud-kcs-help-kbarticles