Documentation

Resolving metadata schema visibility issues for non-admin users in AEMaaCS

Last update: Fri May 23 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

In AEM as a Cloud Service (AEMaaCS) – Assets, users like Contributors or DAM Users can’t see custom metadata schemas because they don’t have read access to the schema folder, but administrators can. To fix this, grant the affected users read access to that folder.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS) - Assets

Issue/Symptoms

  • Custom metadata schemas applied to folders are visible to administrators.
  • Users with standard roles, such as Contributors, only see the default metadata schema when viewing asset properties.
  • Custom metadata schemas applied to folders are visible to administrators.
  • Users with standard roles, such as Contributors, only see the default metadata schema when viewing asset properties.

Resolution resolution

  1. Use asset metadata schemas to apply custom metadata to assets in folders and subfolders. Assign them through Tools > Assets > Metadata Schemas.
  2. Make sure custom schemas are stored under /conf/global/settings/dam/adminui-extension/metadataschema.
  3. In AEM’s Security (Permissions) UI, choose the Contributor/User group and grant jcr:read permission recursively on the schema folder path so they can see custom metadata schemas.
  4. Remove restrictive Access Control List (ACL) rules like rep:glob="" that limit access to only the exact node (for example, /conf) and block access to child nodes. Adjust the ACL to allow recursive jcr:read access so users can access all necessary subpaths.
  5. Make sure the custom schema node is located under /conf/global/settings/dam/adminui-extension/metadataschema. Don’t place it in project-specific paths like /conf/<project>/... unless absolutely necessary, as this can affect visibility.
  6. Create a test Contributor user with minimal group memberships. Then verify that this user can view the custom metadata schema in asset properties to confirm the permissions are correctly set.
  7. Avoid granting overly broad read permissions; instead, target specific paths like /conf/global/settings/dam/adminui-extension/metadataschema. Regularly audit permissions to catch conflicts or restrictive rules, and document any changes to default settings for future reference.

Follow these steps to ensure standard users can view custom asset metadata schemas just like administrators.

Metadata schemas in AEM as a Cloud Service User Guide.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f