Is there a way to separate assets within a portal so that they are only seen by a selected group of users?
Solved! Go to Solution.
Views
Replies
Total Likes
Couple of documentations
https://www.danklco.com/posts/2022/12/3-simple-rules-for-success-with-aem-acls.html
Please check #2 in the above blog
@Jennifer_ZP , i assume when you portal, you meant in AEM Author? You can create the user groups in AEM and assign the selected set of users to the group. User Group can have the permissions as you need. In your case , you can allow read/write/activate permission for your user group. By default you need to deny read for everyone else.
Couple of documentations
https://www.danklco.com/posts/2022/12/3-simple-rules-for-success-with-aem-acls.html
Please check #2 in the above blog
Your use case seems good fit for collections [0] and CUGs [1]. Not sure if you have a multi tenancy factor too; so that if a user logs in from group X, he/ she sees assets only provided read permission to the group. Multi-tenancy [2] is suitable for authoring environment where as publish tier use cases can easily be implemented using collections and CUGs. A multi tenancy implementation has to consider many aspects of isolating assets and controlling what options could they see. Theoretically needs a bigger planning and of course a grand implementation. These are few options but the overall solution depends on your use case and the scale you want to achieve.
It can be done by creating groups and assigning users to them.
Please find below an Adobe document for your reference.
Views
Likes
Replies
Views
Likes
Replies