Overview
Keep discussions organized per topic, pin decisions, and link work across apps.
Problem
Project chat quickly becomes noisy; key decisions and files get lost in scrollback.
Solution
Use one channel per project with reply-in-thread by default, pins for decisions, and a scoped right-rail for Canvas, Files, and Chronicle.
How it works
Adopt a `#proj-*` naming policy, create threads per work item, attach files via File-Vault, and pin a Channel Canvas as the brief/runbook. Use the command palette to open tickets or tasks directly from messages.
Who is this for
Project Managers
Engineering / Design Leads
Cross-functional Teams
Expected outcomes
- Cleaner channels and faster decisions
- Traceable context linked to work items
Key metrics
Threads per decision (median)
Baseline
1 count
Target
1 count
Decision to pin time (p50)
Baseline
180 minutes
Target
15 minutes
Gallery
Downloads & templates
Security impact
- Messages, files, thread metadata · PII: none by default; depends on content
Compliance
- SOC2
- Retention policies via File-Vault
Availability & next steps
Free
Pro
Enterprise