# Epic COMMS-425 - Enhanced collaboration for documents

Project: Stream Communicator
Status: in specification
URL: https://community.openproject.org/work_packages/COMMS-425

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap |  |
| Date |  |
| Votes |  |
| List |  |
| Target versions | Product Backlog |
| Sprint |  |
| Backlog bucket | Features for Documents |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Documents |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Designer | Parimal Satyal |
| Developers |  |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

# User Problem

## Problem

  - Missing tools for effective asynchronous collaboration on documents.

  - Missing comment threads for asynchronous discussions.

  - Missing notifications for letting colleagues know about comments/mentions.

  - Missing fine-grained access controls for documents.

## Pain

Sending direct messages via chat to colleagues, writing comments in the main text.

# Business Case

## Reach

*90% - most users will at least sometimes collaborate asynchronously with colleagues.*

## Impact

*High - using Chat to coordinate asynchronous work is cumbersome and error prone.*

## Confidence

*Medium - it's generally well understood, but some details are not yet clear.*

## Urgency and Priority

High priority.

## Solution

*How do we solve the user’s problem. What is our “pain killer”? What must we achieve in the first version of the solution in order to achieve value for the user?*

  - Document can be shared with specific people

  - Document visibility can be restricted (only invite, private, ...)

  - **\[Inline comments\]**
    
      - with threads, in notification center, ...

  - General comments

  - @mention users

  - Watchers

  - Notifications for mentions/comments on Notification Center and emails
    
    ### 

## 

## 

# Launch and Growth

## Measures

*How will you know you solved the problem? Please list measurable, quantitative indicators (preferred) or qualitative ways you plan on assessing the solution?*

  - ...

## Messaging

*If you were to write a press release, how would you describe the value to customers?*

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Headline</p></th><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">First Paragraph</p></th><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Customer Quote</p></th><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr></tbody></table></figure>

## Go to market

*How are you planning on getting this into users' hands?*