> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cms/17.latest/extend-your-project/backoffice-extensions/extending-overview/extension-types/workspaces.md).

# Workspaces

Learn about workspace extension types that provide shared functionality and enable communication within workspace environments.

Workspace extensions are specialized components that enhance Umbraco's editing environments for documents, media, and members. They share state through workspace contexts. This enables coordinated functionality like synchronized actions, real-time status updates, and seamless data flow across the editing interface.

## Available Extension Types

Workspace extensions can be grouped into these types:

### Core Extensions

* [**Workspace Context**](/umbraco-cms/17.latest/extend-your-project/backoffice-extensions/extending-overview/extension-types/workspaces/workspace-context.md) - Provides shared state management and communication between workspace extensions
* [**Workspace**](/umbraco-cms/17.latest/extend-your-project/backoffice-extensions/workspaces.md) - Defines the main workspace environment and routing

### User Interface Extensions

* [**Workspace Views**](/umbraco-cms/17.latest/extend-your-project/backoffice-extensions/extending-overview/extension-types/workspaces/workspace-views.md) - Tab-based content areas for organizing different aspects of entity editing
* [**Workspace Footer Apps**](/umbraco-cms/17.latest/extend-your-project/backoffice-extensions/extending-overview/extension-types/workspaces/workspace-footer-apps.md) - Persistent status information and contextual data in the footer area

### Action Extensions

* [**Workspace Actions**](/umbraco-cms/17.latest/extend-your-project/backoffice-extensions/extending-overview/extension-types/workspaces/workspace-editor-actions.md) - Primary action buttons that appear in the workspace footer
* [**Workspace Action Menu Items**](/umbraco-cms/17.latest/extend-your-project/backoffice-extensions/extending-overview/extension-types/workspaces/workspace-action-menu-items.md) - Dropdown menu items that extend workspace actions with additional functionality

## Integration Patterns

Workspace extensions communicate through shared contexts using these patterns:

1. [**Workspace Context**](/umbraco-cms/17.latest/extend-your-project/backoffice-extensions/extending-overview/extension-types/workspaces/workspace-context.md) manages centralized state using observables that automatically notify subscribers of changes
2. [**Workspace Actions**](/umbraco-cms/17.latest/extend-your-project/backoffice-extensions/extending-overview/extension-types/workspaces/workspace-editor-actions.md) consume the context to modify state when users interact with buttons or menu items
3. [**Workspace Action Menu Items**](/umbraco-cms/17.latest/extend-your-project/backoffice-extensions/extending-overview/extension-types/workspaces/workspace-action-menu-items.md) add additional options for workspace actions
4. [**Workspace Views**](/umbraco-cms/17.latest/extend-your-project/backoffice-extensions/extending-overview/extension-types/workspaces/workspace-views.md) observe context state to automatically update their UI when data changes
5. [**Footer Apps**](/umbraco-cms/17.latest/extend-your-project/backoffice-extensions/extending-overview/extension-types/workspaces/workspace-footer-apps.md) monitor context state to display real-time status information

### Communication Flow

```
Workspace Context (State Management)
       ↕️
Workspace Actions (State Modification) 
       ↕️
Workspace Views (State Display)
       ↕️  
Footer Apps (Status Monitoring)
```

{% hint style="info" %}
All workspace extensions are automatically scoped to their workspace instance, ensuring that extensions in different workspaces do not interfere with each other.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-cms/17.latest/extend-your-project/backoffice-extensions/extending-overview/extension-types/workspaces.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.