# Feature OP-19759 - When creating a new meeting, add all project members to the meeting participants by default

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

## 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 |  |
| 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

# Feature Request: Automatically Add Project Members as Meeting Participants

**As a** project member creating a new meeting

**I want to** have all project members automatically added as meeting participants when a new meeting is created

**so that** I do not have to manually select each participant and all relevant project members are included by default.

## Acceptance criteria

*   When a new meeting is created within a project, all current project members are automatically added to the participant list.
    
*   The meeting creator remains able to add or remove participants before saving the meeting.
    
*   Automatically added participants receive the same permissions and notifications as manually added participants.
    
*   Users who are added automatically can still be removed individually before or after the meeting is created, subject to existing permissions.
    
*   The feature works consistently regardless of the number of project members.
    

## Technical notes

*   Retrieve the list of active project members when a new meeting is created.
    
*   Pre-populate the meeting participants list with all project members.
    
*   Ensure participant synchronization occurs only during meeting creation. Subsequent changes to project membership should not automatically update existing meetings unless explicitly implemented in a separate feature.
    
*   Consider performance implications for projects with a large number of members.
    

## Permissions and visibility considerations

### To whom is this feature visible?

*   Users with permission to create meetings within a project.
    

### When is it not visible?

*   When the user does not have permission to create meetings.
    
*   Outside the meeting creation workflow.
    

## Translation considerations

### Key terms and phrases in the key languages

*   Project members
    
*   Meeting participants
    
*   Create meeting
    
*   Automatically add participants
    

## Out of scope

*   Automatically updating participants when project membership changes after a meeting has been created.
    
*   Configurable defaults (e.g., only adding members with specific roles).
    
*   Changes to meeting notification behavior beyond the existing functionality.
    

## To be informed/consulted teams

*   <br>
