Ability to configure Publish option in Assets View | Community
Skip to main content
C
Carlos_Guerrer2
Employee
May 13, 2025
New

Ability to configure Publish option in Assets View

  • May 13, 2025
  • 2 replies
  • 259 views
Request for Feature Enhancement (RFE) Summary: Ability to disable the Publish functionality on Assets View
Use-case:

When using AEM Assets with Dynamic Media with OpenAPIs, the 'Publish' functionality is not relevant anymore as assets are published by 'approving' the asset.
Current/Experienced Behavior: In an architecture based on Assets View and Dynamic Media with OpenAPIs, users see a Publish option, which is not supposed to be used. The Publish prompts occurs upon asset upload, which is confusing for the users.
Improved/Expected Behavior: Ideally, there should be a configuration option to enable or disable the Publish feature depending on the the architecture needs.
Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service - Assets View interface.
Customer-name/Organization name:  
Screenshot (if applicable):  
Code package (if applicable):  

    2 replies

    C
    Carlos_Guerrer2Author
    Employee
    May 15, 2025

    Note that the initial request is for Assets View (not Touch UI), so the previous comment is not applicable.

    K_M_K_Srikanth
    K_M_K_Srikanth
    New Participant
    May 15, 2025

    Has anyone tried using granite:rendercondition to control the visibility of the Publish option in the Assets view?

    It seems like we could overlay the Publish action under /libs/dam/gui/content/assets/jcr:content/actions/secondary/publish into /apps, and then add a granite:rendercondition like this:

     

    /apps/dam/gui/content/assets/jcr:content/actions/secondary/publish └── rendercondition (nt:unstructured) ├── sling:resourceType = "granite/ui/components/coral/foundation/renderconditions/simple" └── expression = "${'publishers' in currentUser.memberOf}"

     

    This would show the button only to users in the publishers group.

    Just wondering if anyone has tried this approach or faced issues applying it in the Assets console?

    Terms & ConditionsAccessibility statement

    Loading footer...