umbraco-conditions

Apply declarative conditions to control Umbraco backoffice extension visibility.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Umbraco extension conditions let you control when and where a backoffice extension (dashboard, view, or action) becomes visible, preventing irrelevant or unauthorized UI from appearing to users.

Core Features & Use Cases

  • Declarative gatekeeping: Define requirements based on section, workspace, user permissions, content type, or other context so extensions only appear when allowed.
  • AND logic across multiple conditions: Combine several checks to enforce complex visibility rules in a single manifest.
  • Custom conditions when built-ins are not enough: Implement a condition by extending UmbConditionBase and set permitted state from observed context.

Quick Start

Fetch the latest Umbraco docs for extension conditions, then generate the required manifest conditions for your extension based on the section/workspace/user/content-type rules you want to enforce.

Frequently Asked Questions about umbraco-conditions

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

FAQPage Schema
How do I restrict Umbraco backoffice extension visibility to specific sections or content types?

You can restrict Umbraco backoffice extension visibility by applying declarative extension conditions based on section, workspace, user permissions, or content type. The extension only renders when all specified condition requirements are satisfied.

Can I combine multiple conditions for a single Umbraco dashboard or view?

Yes, you can combine multiple extension conditions using AND logic in Umbraco. The dashboard, view, or action only appears when all combined condition checks evaluate to true, enforcing complex visibility rules within a single manifest.

How do I create custom Umbraco extension conditions when built-in aliases are not enough?

You create custom Umbraco extension conditions by extending UmbConditionBase and setting the permitted state from observed context. This allows you to gate backoffice dashboards and views beyond the standard built-in condition aliases.

What are Umbraco extension conditions and when do I need them?

Umbraco extension conditions are declarative rules that control when and where backoffice extensions become visible. You need them to prevent irrelevant or unauthorized UI components from appearing to users in the wrong sections or workspaces.

Does this approach work for gating Umbraco actions and views, or just dashboards?

This condition-based gating approach works for Umbraco dashboards, views, and actions alike. Any backoffice extension type can use declarative extension conditions to control its rendering based on section, workspace, or permission context.

Why are my Umbraco backoffice extensions showing up for users without the right permissions?

Your Umbraco extensions are showing for unauthorized users because they lack proper declarative extension conditions. You must apply condition aliases checking user permissions and content type context so the UI only renders when requirements are met.