umbraco-conditions

You can conditionally display Umbraco backoffice extensions by defining Extension Conditions in your manifest. These conditions gate visibility based on section, workspace, user permission, and content type context to prevent UI clutter.

Umbraco extension conditions control when dashboards, workspace views, and actions render in the backoffice. Use them when extension visibility and execution must be restricted to specific backoffice scenarios like particular sections or content types.

Yes, you can combine multiple visibility rules for a single Umbraco dashboard using AND semantics. This requires all configured constraints, such as section alias and workspace content type, to pass before the extension renders.

To create a custom condition for an Umbraco workspace view, implement custom UmbConditionBase logic via the extension API. This allows you to evaluate specific context signals beyond the standard built-in condition aliases.

Yes, restricting Umbraco actions to specific content types is supported. You apply condition-based gatekeeping to action manifests so they only become visible and executable when the required content type context is met.

Extensions show up in wrong sections when manifests lack proper visibility gating. You must apply built-in Umb.Condition aliases or custom logic to restrict rendering to the correct backoffice scenarios and avoid confusing UI.