umbraco-extension-registry

Register, exclude, unregister, and overwrite Umbraco backoffice UI extensions.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/1k-off/umbraco-observability-playground --skill umbraco-extension-registry-1k-off
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: umbraco-extension-registry
Source: https://github.com/1k-off/umbraco-observability-playground/tree/main/.agents/skills/umbraco-extension-registry
Command: npx skills add https://github.com/1k-off/umbraco-observability-playground --skill umbraco-extension-registry-1k-off

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Extension Registry helps you manage and customize Umbraco backoffice UI elements without editing core code, so you can add, hide, or replace backoffice components in a controlled way.

Core Features & Use Cases

  • Register extensions at runtime: Dynamically add dashboards, workspace actions, and other backoffice elements by providing an extension manifest.
  • Exclude or unregister extensions: Hide built-in or previously added UI elements, or remove them so they can be re-registered later.
  • Replace existing extensions: Overwrite default behaviors (such as workspace actions) with your own implementation to change how users work in the backoffice.
  • Use Cases: Tailor backoffice UX per section/user role, create custom dashboards, or swap built-in actions with branded or domain-specific flows.

Quick Start

Use the umbExtensionsRegistry to register, exclude, or replace backoffice extensions during initialization by following the latest Umbraco Extension Registry documentation.

Frequently Asked Questions about umbraco-extension-registry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I customize the Umbraco backoffice without modifying core code?

Use the umbExtensionsRegistry during initialization to dynamically add, hide, or replace backoffice UI components by providing an extension manifest with correct fields like type, alias, and element.

What is the best way to add a custom dashboard to Umbraco at runtime?

Registering extensions at runtime involves supplying an extension manifest to the umbExtensionsRegistry, allowing you to dynamically introduce dashboards or workspace actions without modifying core Umbraco.

Can I hide or replace built-in workspace actions in the Umbraco backoffice?

Yes, you can exclude built-in UI elements to hide them or use the overwrite feature to replace default workspace actions with your own implementation, tailoring the backoffice experience per user role.

Does registering Umbraco extensions require modifying the core application?

No, applying extension manifests with correct fields including type, alias, name, element, and meta allows you to conditionally enable or tailor backoffice UI without touching core Umbraco code.

What fields are required in an Umbraco extension manifest?

Required extension manifest fields include type, alias, name, element, and meta, with optional conditions or overwrites to properly register or replace backoffice components via the umbExtensionsRegistry.

When should I unregister an extension instead of excluding it?

Unregistering removes the extension entirely from the runtime registry allowing for fresh re-registration later, while excluding merely hides the UI element without removing its underlying registration.