Account – Workspace – Knowledge base

Route

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

Purpose (business goal)

Provide a workspace-scoped entry point for knowledge base visibility and management.

Users can manage the same knowledge bases either:

• from this workspace surface (scoped to the selected workspace), or
• from Account → Knowledge Bases (knowledge-bases.md), which lists KBs across all accessible workspaces.

User roles & permissions

• Workspace Admin, Manager (read)
• Permissions: kb.view (TBD)

Reference: Roles & Permissions Model

Layout structure

• KB summary (draft/published)
• Links to KB management under /account/knowledge-bases (typically pre-filtered to this workspace) (TBD)

Components used

• Knowledge Base Card: Component: Knowledge Base Card

States

• Empty: no KB exists
• Loading: fetch KB status
• Error: KB service unavailable
• Complete: KB summary displayed

Business logic (high-level)

• KB publish status affects app readiness.
• This surface must only show KBs and status for the selected workspace.

Domain refs: Domain: Knowledge Bases

API dependencies

• GET /knowledge-bases?workspace_id=...

Enterprise constraints

• KB visibility and status are strictly workspace-scoped.
• This page should not expose KB content beyond what the user is authorized to view (TBD).

Edge cases

• Workspace has no KB; show activation guidance and link to create KB (TBD).
• KB exists but user lacks edit/publish permissions; show read-only status (TBD).

Security & compliance considerations

• Permission checks for KB visibility

Reference: Security & Compliance

Analytics events (if applicable)

• kb.published (when publish is triggered from linked flows)

Reference: Analytics Events (MVP)