This document defines the technical direction for the Open edX Console from MVP to a robust product. It complements the Console PRD by focusing on the architecture, system design, extensibility, and service integration.

The goal is to support current requirements, such as centralized role and permission management, while laying a solid foundation for future extensions and platform-wide administration capabilities.

This document provides a shared understanding of how the Console is expected to work from a technical perspective. It guides implementation and decision-making across frontend, backend, and integration layers.

It does not define functionality (which is covered in the PRD), but instead addresses how key features will be built and scaled across Open edX services.

The Console design is organized around three technical focus areas. Each one addresses a major architectural concern and proposes how the system should behave in that dimension.

Where does the Console live? How is it built? How will it evolve?

The Console will eventually be built as a standalone MFE using the Open edX standards. It will start by connecting directly to Django plugins from the authoring MFE for administrative operations and gradually evolve into a centralized, extensible platform with a dedicated backend console-specific definitions.

See more details here: Foundations and Technical EvolutionPreview

How can the Console support external contributions and dynamic behavior?

The Console will offer defined entry points to add new panels, extend workflows, and package multi-layer bundles (Django plugins, UI plugins, or operational plugins). Extensibility will start with limited customization in the MVP and expand to full extension management, aligned with the Console’s phased rollout.

See more details here: Extensibility and Pluggability FrameworkPreview

How does the Console interact with LMS, CMS, and other services?

The Console will integrate with Open edX through in-context and standalone panels in MFEs, service-specific administrative APIs in LMS, CMS, Credentials, and other IDAs, and instance-level operations via Tutor. Early phases will use direct API calls from the MFE; later phases will centralize communication through the Console IDA for consistent routing (when needed) and configuration handling.

See more details here: Integrations with Open edX EcosystemPreview