# Feature MEET-431 - Allow adding groups as participants

Project: Stream Meetings
Status: new
URL: https://community.openproject.org/work_packages/MEET-431

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | High |
| Target versions | Product Backlog |
| Votes | 1 |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_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 |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Build Number |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

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

## Estimates and progress

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

## Description

**As** an organizer of meetings  
**I want to** invite groups to a meeting or meeting series  
**so that** I don't have to invite everyone one by one

**Acceptance criteria**

  - Participation dialog allows selecting participants

  - Either:
    
      - We extend the group one time to all its members
        
          - *inconsistent with other places of the application, but easier to implement*
    
      - We allow group memberships that are not extended
        
          - *Complexity in all places where you need to check whether you are participating in a meeting*
        
          - *will result in failure to track RSVP/attendance*
    
      - We allow group memberships, and keep its members in sync with participant
        
          - *Complexity as with other memberships (projects)*

**Technical notes**

  - Groups expanding memberships is very hard to implement as we've seen with memberships

  - Memberships there are dynamically extended, so whenever the group membership changes, its members need to be updated
    
    <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* 

**Out of scope**

  - 
    <br>

*Set the* **To be informed/consulted teams** *field to include all teams necessary to be informed of the changes.*
