Overview

This flow documents the workspace lifecycle from creation through configuration and eventual deletion. A workspace serves as the container for dashboards and saved queries, providing organizational structure and access control boundaries.

The workspace lifecycle involves creating the container, initializing user preferences, populating with content, and eventual cleanup.

Workspace creation

Users create workspaces to organize related analytical artifacts. A workspace provides isolation for dashboards and saved queries, enabling focused analysis on specific projects or data domains.

The WorkspaceCreated event captures the workspace identifier, owner, and initial metadata such as name and description.

Preference initialization

After workspace creation, user preferences are initialized with sensible defaults. Preferences include theme settings, default catalog selection, and UI state persistence.

Preferences are user-scoped rather than workspace-scoped, applying across all workspaces the user accesses.

Content population

Workspaces are populated with dashboards and saved queries over time. Each dashboard and query belongs to exactly one workspace, identified by the workspaceId field in all workspace domain events.

Content can be added in any order. Users typically create saved queries first, then visualize results in dashboards.

Workspace deletion

Workspaces may be deleted when no longer needed. Deletion should cascade to contained dashboards and queries, or require explicit cleanup first depending on policy.

Soft delete with recovery period is recommended for enterprise deployments.