Sitecore

Hello everyone! I hope you’re doing well. Let’s continue exploring how we can customize asset action visibility in a Content Hub external component. In my previous blog, Beyond Permissions: Customizing Asset Actions in Content Hub , we discussed how to hide the Download button on the asset search page for assets belonging to a specific source system. However, there’s another important aspect we haven’t covered yet: What happens when a user tries to download the same asset using a bulk operation? Hiding the Download button from the asset card is one thing, but ensuring that the same restriction applies to bulk operations is equally important. In this blog, we’ll explore how we can handle this scenario using a Content Hub external component. When policies cannot fully address this requirement, we can still rely on our trump card: an external component. In this scenario, we’ll continue using the same source system, KOL , to demonstrate how we can control asset actions for assets belo...

Hello everyone, Welcome to another blogpost. This blog will focus on Sitecore Content Hub development. We will discuss a use case that is highly relevant to practical development and reflects real-world business scenario. Let's get started without wasting any more time. Sitecore Content Hub provides a powerful security model through User Groups, Policies, Permissions, and Conditions. While these controls determine what users can do within the platform, they do not always control what users see in the user interface. Our blog will be exactly around this functionality. We received a requirement to restrict the download of certain assets from the Asset Search page. Specifically, any asset tagged with a particular taxonomy value should not be available for download by users. We explored using policies and permissions, particularly DRM rights in Content Hub, to address this requirement. However, none of the available configuration options provided a way to hide the Download button on...