02 — Workbench Information Architecture
Navigation order
IW
├── Home
├── My Work
├── Communications
├── Personal
├── Work
├── Platform
└── Administration
Daily work must remain above platform management.
Home
Route: /app/home
Shows daily priorities, active work, recent items, approvals, notifications, meetings, activation issues, and small contextual Twin signals.
My Work
Base route: /app/my-work
- Inbox
- Tasks
- My Queue
- Approvals
- Notifications
- Recent Work
- Favorites
These surfaces aggregate work assigned to the user regardless of source system or department.
Communications
Base route: /app/communications
- Activity Feed
- Calendar
- Meetings
- Chat
- Calls
- Shared Documents
Each communication item may link to accounts, projects, tasks, documents, meetings, and proposals.
Personal
Base route: /app/personal
- Notes
- Knowledge Base
- Brainstorming Sessions
- Activity
- Finance Manager
Personal surfaces default to private or user-scoped local state. Promotion into shared or canonical state must be represented as a proposal.
Work
Base route: /app/work/:department/:view
Work is generated from role, department, industry, tenant configuration, and permissions. It must list every valid resolved view for the assigned department.
Example:
Work
└── Account Success
├── Portfolio
├── Accounts
├── Renewals
├── Risks
├── Adoption
├── Escalations
├── Success Plans
├── QBRs
├── Health
└── Expansion
The actual labels and component mapping must come from the repository inventory.
Platform
Base route: /app/platform
Available to authorized users:
- Integration Manager
- Connector Marketplace
- Activation Hub
- Capability Manager
- Knowledge
- Memory & Continuity
- Automation
- Pipelines
- Governance
Customer Zero or platform-operator additions:
- MCP Pool
- AI Models
- Agents
- Spine Network
- Observability
- Deployments
Administration
Base route: /app/admin
- Organizations
- Users
- Roles
- Permissions
- Audit
- Billing
- Deployments
- API Keys
- Security
Administration is permission-filtered and collapsed by default.
Sidebar behavior
- Work is expanded by default.
- Platform and Administration are collapsed by default.
- Only authorized entries are rendered.
- Active nested routes keep their parent expanded.
- Work navigation is scrollable when many views exist.
- Mobile uses an off-canvas drawer with nested Work navigation.
- Workspace and role switching appears near the sidebar header.
Status indicators
Navigation entries may display unread counts, approval counts, running states, warnings, failures, restrictions, or Twin recommendations. Indicators must represent local demo state accurately and must not imply a backend event occurred.