umbraco-collection-action

To add a custom button to an Umbraco backoffice collection toolbar, you implement a collection action by creating an extension-registry manifest entry and an action class extending UmbCollectionActionBase. This allows editors to execute custom code or navigate to a URL for the whole collection.

Yes, Umbraco collection actions support advanced UX patterns like modal-driven workflows. You can configure the action class to trigger exports via modals or display additional options dropdown indicators when the action requires user input before executing.

You restrict an Umbraco collection action to specific collections using UI conditions. You can match the action to the right collection by applying conditions based on common collection aliases like document, media, or members.

An Umbraco collection action is used to perform collection-level tasks directly from a collection's toolbar in the backoffice. It enables editors to execute whole-collection operations like creating new items, triggering exports, or navigating to a specific URL.

Yes, you need TypeScript to create an Umbraco collection toolbar action. The implementation requires producing a compatible action class that extends UmbCollectionActionBase and integrates with the Umbraco extension registry using TypeScript.

If your Umbraco collection action is not showing up in the backoffice toolbar, verify your extension-registry manifest entry is correct and your UI conditions match the target collection alias. Fetching the latest Umbraco documentation helps ensure the manifest and action class are properly configured.