Begin of the insertion**As a** meeting participantEnd of the insertion Begin of the deletion **As** a \[enter role of user\]End of the deletion
**I Begin of the insertionwant** to view meeting details, participants, and attachments in dedicated tabsEnd of the insertion Begin of the deletion want to** \[enter objective\]End of the deletion
**so that** Begin of the insertionI can quickly understand logistics, who is involved, and access relevant files from my phone.End of the insertion Begin of the deletion \[enter desired result\]End of the deletion

Begin of the insertion### Acceptance CriteriaEnd of the insertion Begin of the deletion **Acceptance criteria**End of the deletion

* Begin of the insertionThe meeting screen provides a tab bar with: **Agenda**, **Backlog**, **Details**, **Participants**, **Attachments**.

End of the insertion Begin of the deletion <br>


**Technical notes**

End of the deletion * Begin of the insertionThe selected tab is visually highlightedEnd of the insertion Begin of the deletion <br>


**PermissionsEnd of the deletion and Begin of the insertionpersists while staying on the meeting screen.

End of the insertion Begin of the deletion visibility considerations**

End of the deletion * Begin of the insertionThe **Details** tab displays a “Meeting details” section containing:

* Meeting series (ifEnd of the insertion Begin of the deletion _To whomEnd of the deletion is Begin of the insertionpart of a series)

End of the insertion Begin of the deletion this feature visible?_

End of the deletion * Begin of the insertionDate

* Start time

* Duration

* Location (as text; if itEnd of the insertion Begin of the deletion _WhenEnd of the deletion is Begin of the insertiona URL,End of the insertion it Begin of the insertionis rendered as a tappable link)

End of the insertion Begin of the deletion not visible?_


**Translation considerations**

End of the deletion * Begin of the insertionThe **Details** tab displays also the “Meeting status” section:

* Shows the current meeting status as a status pill (e.g., “Open”)

* Shows descriptive helper text explaining what the status means (as per product copy, same as in the web app)

* The **Details** tab displays an “Email calendar updates” section:

* Shows whether calendar updates are enabled/disabled

* Shows a short explanatory text (as per product copy, depending if it is a series or not)

* Provides a tappable link “edit the series template” that opens the series template (in-app if supported when <mention class="mention" data-id="75224" data-type="work_package" data-text="###75224">###75224</mention> is implemented)

* If any field is missing (e.g., no location), the corresponding row is displayed empty.

* Pull-to-refresh on the meeting screen refreshes the currently visible tab content.

* If the meeting cannot be loaded (network/server error), an error state is shown with a retry action.

* If the user lacks permission to view the meeting, the screen shows an access-denied state (no partial data).

* The **Participants** tab is a &quot;copy&quot; of the watchers tab on Work packages that shows:

* A search field to quickly find participants by name

* A primary action button **Add participant**

* A list of current participants with avatar + display name

* “(me)” suffix after the current user

* Tapping **Add participant** opens a participant picker:

* Allows searching users

* Confirms addEnd of the insertion Begin of the deletion _Key termsEnd of the deletion and Begin of the insertionupdates the list immediately on success

* Each participant row provides an overflow menu (“…”) with actions asEnd of the insertion Begin of the deletion phrasesEnd of the deletion in the Begin of the insertionwork packages watchers tab:

* Remove participant (if permitted)

* Removing a participant requires confirmation and updates the list on success.

* If the user lacks permission to manage participants:

* **Add participant** is hidden

* Overflow actions that remove participants are hidden

* Participants list supports incremental loading if the list is long.

* The **Attachments** tab is a the same as in the work packages attachments tab and it shows:

* A search field/filter (by filename)

* A filter control **All types** (default)

* A primary action button **Add attachment**

* A listEnd of the insertion Begin of the deletion key languages_&nbsp;


**OutEnd of the deletion of Begin of the insertionattachments showing:

* Type icon (e.g., document/image)

* Filename/title

* Secondary info (e.g., “added by &lt;user&gt;”, relative timestamp)

* Tapping an attachment opens it:

* If supported in-app (e.g., image/PDF preview), open in-app viewer

* Otherwise, open using the system share/open-in app flow

* Each attachment row provides an overflow menu (“…”) with the same actions available in the work package attachments tab.

* Tapping **Add attachment** allows:

* Uploading from device (files/photos) if supported

* Adding a photo from camera/gallery if supported

* Taking a photo or video

* If an upload fails, the user sees an error and can retry.

* If the user lacks permission to add/remove attachments:

* **Add attachment** is hidden or disabled

* Remove action is hidden


### Technical NotesEnd of the insertion Begin of the deletion scope**End of the deletion

* Begin of the insertionData model

* Meeting entity: includes meeting series reference, project reference, status, scheduling fields (date/time/duration), location string/URL, and settings for calendar updates.

* Participants: list of user references (id, name, avatar URL).

* Attachments: list of attachment references (id, filename, content type/type, createdBy, createdAt, file URL / download endpoint).

* API dependencies / contracts (OpenProject API v3 aligned where relevant)

* GET meeting details endpoint returning meeting + tabs data or individual endpoints:

* `/meetings/:id` (details)

* `/meetings/:id/participants`

* `/meetings/:id/attachments`

* Participant management:

* POST add participant(s)

* DELETE remove participant

* Attachment management:

* POST upload attachment (multipart or upload session)

* DELETE remove attachment

* GET download/open attachment (signed URL or authenticated streaming)

* Frontend vs backend responsibilities

* Backend enforces permissions; frontend must also hide/disable actions based on capability flags returned by API (preferred) or inferred permissions.

* Backend provides localized-ready status strings or stable status keys; frontend displays localized labels.

* Caching / state / performance

* Cache meeting shell data (title, tabs, status) for quick navigation; refresh on pull-to-refresh and on screen focus.

* Tab content shouldEnd of the insertion Begin of the deletion <br>


_Set the_ **ToEnd of the deletion be Begin of the insertionloaded lazily per tab (Participants/Attachments can be fetched when opened) with a small prefetch optional for perceived speed.

* Use pagination for participants/attachments if endpoints are large; search should be client-side for small lists, server-side for large lists (capability-dependent).

* Offline / poor network

* If cached content exists, show it with an “out of date” indication and allow manual refresh.

* Mutations (add/remove participant, upload/remove attachment) require connectivity; show clear error when offline.

* UI parity with Work Package details

* Reuse existing row components, section headers, status pill component, overflow menu component, and “Add …” toolbar/button patterns from the Work Package details implementation.


### Permissions and Visibility Considerations

* Viewing

* Only users with permissionEnd of the insertion Begin of the deletion informed/consulted teams** _fieldEnd of the deletion to Begin of the insertionview the meeting (via project membership/roles) can see Details/Participants/Attachments.

* Attachments must notEnd of the insertion Begin of the deletion include all teams necessary toEnd of the deletion be Begin of the insertionaccessible via direct URL without authentication/authorization.

* Editing

* Adding/removing participants requires a specific meeting-management permission (or equivalent project permission).

* Adding/removing attachments requires attachment permission (or equivalent).

* Conditional UI

* If user cannot edit: hide/disable “Add participant”, “Add attachment”, and destructive overflow actions.

* If user can view but not manage: still show lists read-only.

* Privacy

* Participant search/picker must not leak users outside allowed scope (project-visible users as defined by server rules).


### Translation Considerations

* Must be localizable:

* Tab labels: Agenda, Backlog, Details, Participants, Attachments

* Section headers: Meeting details, Meeting status, Email calendar updates

* Button labels: Add participant, Add attachment

* Filter labels: All types

* Helper texts under status and calendar updates

* Error states and confirmation dialogs (e.g., remove participant/attachment)

* Must NOT be translated:

* Filenames (attachment names)

* IDs, stable keys, URLs

* User-provided location text (unless it is explicitly a system-generated label)


### OutEnd of the insertion Begin of the deletion informedEnd of the deletion of Begin of the insertionScope

* Editing meeting agenda/backlog content as it will be implemented in <mention class="mention" data-id="75100" data-type="work_package" data-text="###75100">###75100</mention> and <mention class="mention" data-id="75168" data-type="work_package" data-text="###75168">###75168</mention>.

* Editing meeting series configuration insideEnd of the insertion the Begin of the insertionapp as it will be implemented in <mention class="mention" data-id="75224" data-type="work_package" data-text="###75224">###75224</mention>.

* Advanced attachment features such as versioning, renaming, or tagging.

* Inviting external (non-user) participants via email.

* Full offline mutation support (queueing uploads/removals for later).End of the insertion Begin of the deletion changes._End of the deletion