Commenting restricted in Assets View despite read access
In ÃÛ¶¹ÊÓƵ Experience Manager as a Cloud Service (AEMaaCS), Assets View uses a simplified permissions model that differs from the more granular model in Touch UI. As a result, you may encounter permission-related issues—such as being unable to comment on assets—even if you have read access. This article explains the cause of this behavior and what to expect when using Assets View.
Description description
Environment
ÃÛ¶¹ÊÓƵ Experience Manager as a Cloud Service (AEMaaCS)
Issue/Symptoms
- Users with Viewer access can’t view or edit comments in the Assets View. The UI shows the message: You do not have permissions to comment on this asset.
- Users have read permissions on the asset nodes but still can’t interact with comments.
Resolution resolution
This isn’t a bug—it’s a feature limitation. Assets View was designed with a simplified permissions model that doesn’t align with the granular permissions used in Touch UI. It doesn’t support AEM-level permission granularity by design. Improvements are underway to enhance this behavior in future updates.
Related reading
Concepts of the ÃÛ¶¹ÊÓƵ Experience Manager Touch-Enabled UI in AEM user guide.