Product: Notara (note-taking app) Author: Product Team Status: Draft Target release: Q3 2026
People don't think alone. Teams use Notara individually, then paste notes into Slack, forward exports by email, and lose the thread. Collaboration happens around the product, not inside it. Knowledge fragments. Context dies in transit.
The gap is structural. Notara has no shared surface. Every note is a private document until someone exports it, at which point it stops being a living note and becomes a static artifact.
1. The team lead Sofia runs a three-person content team. She creates a shared workspace, adds her colleagues, and pins the editorial calendar note to the top. Her team sees it immediately. Nobody asks where the calendar lives.
2. The async collaborator Marcus works across time zones. He opens a shared workspace, reads his teammate's draft research notes, appends his own findings, and tags the section as ready for review. His teammate sees the update the next morning without a single forwarded email.
3. The solo contributor Yuki wants to share one note from her private workspace without exposing everything else. She moves that note into a shared workspace, keeps her other notes private, and controls what her manager can see.
4. The workspace viewer A project stakeholder needs read access. She receives an invite, browses the workspace without editing rights, and pulls context she needs without disrupting the working notes.
In - Create, rename, and delete shared workspaces - Invite members by email; roles: owner, editor, viewer - Real-time sync of note content across members (last-write-wins, conflict flagged) - Shared workspace appears in each member's sidebar under a "Shared" section - Move notes between personal and shared workspaces - Activity log: who changed what, when (last 30 days) - Notifications: new note added, note edited (daily digest by default)
Out - Simultaneous cursor presence - Inline comments or threaded discussion - Workspace templates - Guest access without a Notara account - Mobile-specific workspace UI (desktop web only for launch)
| Metric | Target at 90 days post-launch |
|---|---|
| Workspaces created per active team account | ≥ 1.5 |
| % of invited members who open workspace within 48 hrs | ≥ 60% |
| Weekly active workspace contributors (editor role) | ≥ 40% of editors invited |
| Support tickets about lost shared notes | < 5 per 1,000 workspaces |
| 30-day workspace retention (workspace still active) | ≥ 70% |
Conflict resolution creates trust failures. Last-write-wins is simple, but users who lose changes without warning will disengage. Mitigation: surface a conflict banner with a one-click diff for the previous 60 seconds.
Notification fatigue. If every keystroke triggers an alert, members disable notifications and miss what matters. Mitigation: batch edits into daily digests; let users set per-workspace alert frequency.
Permission confusion. Users will misread "viewer" as "can comment." Mitigation: role labels show explicit capability text on the invite screen and in workspace settings.
Adoption without a champion. Shared workspaces require someone to invite teammates. Single-user accounts won't trigger the feature at all. Mitigation: surface an in-app prompt after a user creates three or more notes in the same week, with a direct link to create a shared workspace.