# Feature OP-19983 - Collaborative documents connected to meetings

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-19983

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Meetings, Modules and project features / Documents |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As a** meeting organizer,  
**I want** the ability to create and manage collaborative documents (documents module) directly from within the meeting interface  
**so that** all attendees can collaborate in real-time based on the context of the discussion.

Current status:

Currently, users can create documents via the separate Documents module, but these documents are not automatically linked or associated with the specific meeting, making them difficult to track and reference.

**Acceptance criteria**

*   Users can create a new document from within the meeting (e.g. after starting a meeting)
    
*   It is easy for users to open and work on this document during the meeting
    
*   The resulting document is permanentely linked to the meeting (visible link in meeting and in document in documents module)
    

**Technical notes**

*   <br>
    

**Permissions and visibility considerations**

*   _To whom is this feature visible?_
    
*   _When is it not visible?_
    

**Translation considerations**

*   _Key terms and phrases in the key languages_&nbsp;
    

**Out of scope**

*   <br>
    

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
