In the file forward flow, when a file is shared and forwarded across multiple peers, the access control visibility and UI behavior are inconsistent with the expected design.
Scenario:
Peer 1 shares a file abc.png.prv with Peer 2.
Peer 2 forwards the same file to Peer 3, Peer 4, and Peer 5.
Current Behavior
The File Access Control page visibility is unclear/inconsistent:
It should be visible in the Peer 1 ↔ Peer 2 conversation on Peer 2’s device.
On Peer 3, Peer 4, and Peer 5 screens:
The forwarded file is clickable
A bell icon is visible
The file message box contains extra UI elements instead of being minimal
Expected Behavior
Access Control Page
The File Access Control page must be visible only in:
Peer 1 ↔ Peer 2 conversation
On Peer 2’s device
Forwarded Recipients (Peer 3, 4, 5)
The forwarded file must NOT be clickable
No bell icon should be displayed
The message box should be clean, showing only:
File name
“Forwarded message” label
Steps to Reproduce
Peer 1 shares abc.png.prv with Peer 2.
Open the conversation on Peer 2’s device.
Peer 2 forwards the file to Peer 3, Peer 4, and Peer 5.
Check:
Access control visibility in Peer 1 ↔ Peer 2 chat
File UI behavior in Peer 3/4/5 chats
Acceptance Criteria
Access Control page is visible only in Peer 1 ↔ Peer 2 chat on Peer 2’s device
Forwarded file is non-clickable for Peer 3/4/5
No bell icon shown for forwarded recipients
Message box UI displays only “Forwarded message” label and file info
In the file forward flow, when a file is shared and forwarded across multiple peers, the access control visibility and UI behavior are inconsistent with the expected design.
Scenario:
Peer 1 shares a file abc.png.prv with Peer 2.
Peer 2 forwards the same file to Peer 3, Peer 4, and Peer 5.
Current Behavior
The File Access Control page visibility is unclear/inconsistent:
It should be visible in the Peer 1 ↔ Peer 2 conversation on Peer 2’s device.
On Peer 3, Peer 4, and Peer 5 screens:
The forwarded file is clickable
A bell icon is visible
The file message box contains extra UI elements instead of being minimal
Expected Behavior
Access Control Page
The File Access Control page must be visible only in:
Peer 1 ↔ Peer 2 conversation
On Peer 2’s device
Forwarded Recipients (Peer 3, 4, 5)
The forwarded file must NOT be clickable
No bell icon should be displayed
The message box should be clean, showing only:
File name
“Forwarded message” label
Steps to Reproduce
Peer 1 shares abc.png.prv with Peer 2.
Open the conversation on Peer 2’s device.
Peer 2 forwards the file to Peer 3, Peer 4, and Peer 5.
Check:
Access control visibility in Peer 1 ↔ Peer 2 chat
File UI behavior in Peer 3/4/5 chats
Acceptance Criteria
Access Control page is visible only in Peer 1 ↔ Peer 2 chat on Peer 2’s device
Forwarded file is non-clickable for Peer 3/4/5
No bell icon shown for forwarded recipients
Message box UI displays only “Forwarded message” label and file info