umbraco-global-context

Implement global contexts in the Umbraco backoffice for type-safe session-wide data sharing.

26|13|Updated Nov 30, 2025

Search Tags:#typescript #context #global state #extension development #umbraco #backoffice

Ready to run

npx skills add https://github.com/umbraco/Umbraco-CMS-Backoffice-Skills --skill umbraco-global-context

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: umbraco-global-context
Source: https://github.com/umbraco/Umbraco-CMS-Backoffice-Skills/tree/main/plugins/umbraco-backoffice-skills/skills/umbraco-global-context
Command: npx skills add https://github.com/umbraco/Umbraco-CMS-Backoffice-Skills --skill umbraco-global-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the need for a centralized, type-safe way to share data and functions across the entire Umbraco backoffice session, enabling better coordination between different extensions.

Core Features & Use Cases

Global State Management: Implement persistent, session-wide data sharing.
Service Coordination: Centralize common services or utilities for use by multiple backoffice components.
Use Case: Imagine needing to share the currently logged-in user's preferences or a global notification service across several different backoffice sections. This skill provides the mechanism to do so reliably.

Quick Start

Use the umbraco-global-context skill to create a new global context for managing user settings.

Frequently Asked Questions about umbraco-global-context

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

FAQPage Schema

How do I share global state across the Umbraco backoffice?▼

To share global state across the Umbraco backoffice, implement a global context using the Context API. This provides a centralized, type-safe mechanism for session-wide data sharing and inter-extension coordination.

How does inter-extension communication work in the Umbraco backoffice?▼

Inter-extension communication works by consuming a shared global context. Extensions access centralized services and type-safe data through the Foundation patterns, enabling reliable coordination between different backoffice components.

What is the best way to manage centralized backoffice services for multiple Umbraco extensions?▼

The best way to manage centralized services is creating a global context. This approach centralizes common utilities or data, such as user preferences, making them reliably accessible across multiple backoffice sections during the session.

Can I use TypeScript to ensure type safety when sharing data between Umbraco extensions?▼

Yes, you can use TypeScript to ensure type safety when sharing data. The global context mechanism is designed to provide type-safe data and functions across the entire Umbraco backoffice session.

Do I need to follow specific API patterns for Umbraco extension development?▼

Yes, you need to follow Umbraco's Context API and Foundation patterns. Adherence to these specific patterns is required for properly implementing and consuming global contexts in extension development.

When should I use a global context instead of local component state in Umbraco?▼

Use a global context when you need persistent, session-wide data sharing across different backoffice sections. If the data is only needed within a single isolated component, local state is more appropriate.