skills.rest
albanist
albanistCOMMUNITY
Explore all skills by this author →
GitHub

umbraco-conditions

Define conditional visibility rules for Umbraco backoffice extensions.

4|Updated Mar 6, 2026
Search Tags:#extension#manifest#visibility#conditions#umbraco#backoffice
One-click install
npx skills add https://github.com/albanist/umbraco_CLI --skill umbraco-conditions-albanist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: umbraco-conditions
Source: https://github.com/albanist/umbraco_CLI/tree/main/skills/foundation/umbraco-conditions
Command: npx skills add https://github.com/albanist/umbraco_CLI --skill umbraco-conditions-albanist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps manage when and where custom extensions appear in the Umbraco backoffice, preventing clutter and ensuring relevance by defining specific requirements for their visibility.

Core Features & Use Cases

  • Conditional Visibility: Define rules based on section, workspace, content type, or user permissions.
  • Gatekeeping Extensions: Ensure extensions only show when the context is appropriate.
  • Use Case: You can configure a custom dashboard to only appear in the 'Content' section and only when viewing a specific content type like 'BlogPost'.

Quick Start

Use the umbraco-conditions skill to add a condition to a manifest that shows an extension only in the 'Content' section.

Frequently Asked Questions about umbraco-conditions

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

FAQPage Schema
How do I control Umbraco backoffice extension visibility based on user context?▼

To control Umbraco backoffice extension visibility, you apply conditions to a manifest that define specific rules based on section aliases, workspace types, content types, and user permissions. This ensures extensions only appear in relevant contexts.

What are Umbraco manifest conditions used for?▼

Umbraco manifest conditions are used for gatekeeping extensions, preventing backoffice clutter by ensuring dashboards, workspace views, and entity actions only display when specific context requirements like section aliases are met.

Can I show a custom dashboard only for a specific content type in Umbraco?▼

Yes, you can show a custom dashboard only for a specific content type in Umbraco by defining a condition in your manifest that restricts visibility to a particular workspace type and content type like 'BlogPost'.

How do I configure an Umbraco extension to only appear in the Content section?▼

You configure an Umbraco extension to only appear in the Content section by adding a condition to its manifest that specifies the appropriate section alias as a requirement for visibility.

What types of Umbraco backoffice extensions support conditional visibility rules?▼

Conditional visibility rules in the Umbraco backoffice apply to dashboards, workspace views, and entity actions. This allows granular control over extension availability across different sections and content types.

Related Skills

Explore More Software Engineering Skills→
umbracoumbraco
26

umbraco-conditions

Evaluate contextual criteria to control Umbraco backoffice extension visibility.

Official
Intermediate
albanistalbanist
4

umbraco-workspace

Create custom routable workspaces for entity types in the Umbraco backoffice.

Community
Advanced
1k-off1k-off
1

umbraco-sections

Create Umbraco backoffice section manifests with dashboards and sidebars.

Community
Intermediate
kraftvaerkkraftvaerk

umbraco-property-editor-schema

Implement Umbraco property editor schemas with C# and manifest configurations.

Official
Intermediate