Content Hub Custom Action Button on Asset Card

​@ShannaBo 

We reviewed the currently available Content Hub documentation. The officially documented capabilities today focus on configuring the Content Hub experience — for example asset card metadata, branding, search behavior, and custom links. We did not find public documentation describing a generally available, self-service method to add a custom action button directly on the Content Hub asset card.

If your use case requires a custom workflow or button in Content Hub, we should treat that as a feature validation / product discussion with Adobe rather than commit to it as an out-of-the-box documented capability.

As a related point, Adobe does document UI extensibility for AEM Assets View, but that is a different surface from Content Hub, so it should not be assumed to apply the same way to Content Hub asset cards.

• Configure Content Hub user interface
• Enable UI extensibility in AEM Assets View

Hi ​@ShannaBo ,

The custom action button in Content Hub is part of Content Hub extensibility via AppBuilder. It is intended to let customers add their own UI action around assets, such as sending an asset into another workflow or opening a custom interaction panel.

Please refer to the below documentation that may help.

https://developer.adobe.com/uix/docs/services/aem-assets-view/api/browse-view/

​@ShannaBo This is a really interesting question, thanks for raising it, as this comes up quite a bit when teams start extending Content Hub.
 

From the responses above, it looks like there are two slightly different contexts being discussed, so just to help clarify:

• Out-of-the-box, there isn’t currently a self-service way to configure a custom action button directly on the Content Hub asset card via standard settings/config (as mentioned earlier).
• However, if you’re looking for custom actions (like triggering workflows, integrations, or external panels), this is supported through Content Hub extensibility using AppBuilder, where you can extend the UI and attach custom actions to assets.
   

So effectively, this isn’t a simple configuration-level feature yet, but more of an extensibility/custom development scenario depending on your use case.
 

One thing worth considering is how tightly the action needs to be integrated into the asset card UI vs. whether it can be handled via a panel/workflow extension, that usually influences the approach quite a bit.
 

Curious what specific use case you’re targeting (e.g., workflow trigger, external system integration, metadata action)? That might help narrow down the best pattern here.