Account – Workspace

Route

• Path: /account/workspaces/:workspaceId (TBD)
• Parent: workspaces.md
• Children:
  • workspace-knowledge-base.md
  • workspace-users.md
  • workspace-user-activity.md

Purpose (business goal)

Provide a workspace-level hub for managing KB, users, and user activity for a single workspace.

User roles & permissions

• Workspace Admin
• Permissions: workspace.view, plus child-page permissions

Reference: Roles & Permissions Model

Layout structure

• Workspace header (name/status)
• Tabs/nav: Knowledge base / Users / User activity
• Content region

Components used

• Workspace Card: Component: Workspace Card

States

• Empty: workspace exists but no KB/users configured
• Loading: fetch workspace details
• Error: not found / access denied
• Complete: workspace hub renders

Business logic (high-level)

• Workspace scope selection is applied to child pages.

Domain refs: Domain: Workspaces

API dependencies

• GET /workspaces/{id}

Enterprise constraints

• All displayed/configurable data must be strictly scoped to the selected workspace.
• Workspace context changes must not “bleed” across tabs/apps.

Edge cases

• Workspace membership revoked while viewing the page.
• Workspace deleted/disabled; route should return Not Found or access denied (TBD).

Security & compliance considerations

• Prevent cross-workspace data leakage

Reference: Security & Compliance

Analytics events (if applicable)

• workspace.switched (when changing the active workspace context)

Reference: Analytics Events (MVP)