Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Creating knowledge site using AEM. User should be able to upload /download different type of assets

tempUser12345
Level 1
Level 1

Creating knowledge site using AEM. User should be able to create folders, upload /download different type of assets, create microsites/pages etc. Workflow to be their at different levels along with authorization for asset access

 

Please suggest design recommendations. Does AEM provides such OOTB components?

1 Accepted Solution
Sanket_Kumbharkhane
Correct answer by
Level 4
Level 4

You can refer to "Asset Share Commons", below are some of the features you can consider and customize as per your requirement 

 

  • Out of the box components that can be used to customize the experience, but you can create your components if needed.
  • Customizable in layout and view 
  • Assets can be made available to a set of defined people or everyone.
  • Support for Editable Templates and Responsive Grid features

 https://experienceleague.adobe.com/docs/experience-manager-learn/assets/sharing/assets-share/asset-s...

View solution in original post

3 Replies
Sanket_Kumbharkhane
Correct answer by
Level 4
Level 4

You can refer to "Asset Share Commons", below are some of the features you can consider and customize as per your requirement 

 

  • Out of the box components that can be used to customize the experience, but you can create your components if needed.
  • Customizable in layout and view 
  • Assets can be made available to a set of defined people or everyone.
  • Support for Editable Templates and Responsive Grid features

 https://experienceleague.adobe.com/docs/experience-manager-learn/assets/sharing/assets-share/asset-s...

View solution in original post

tempUser12345
Level 1
Level 1

Thanks Sanket. Assets Share Commons does help with some part of the requirement. Wanted to understand, is it good practice to expose this to end user along with customization to allow create/delete folders and upload/edit/delete assets? or complete custom solution should be build for same.

I would suggest building a custom solution around it. Giving too much authority to the end-user can be risky. The best is to allow only upload option for end-user but in that case, too, build custom workflow & approval process so that no one able to upload objectionable content.