Currently, in CometChat Calls (including the Flutter UI Kit), participants have the ability to mute other users through the participant actions menu. This behavior is not ideal for many applications, as it allows users to control other participants’ audio without restriction, resulting in a poor user experience and reduced sense of personal control.
To address this, we propose introducing granular permission controls for participant audio actions. This would include the ability to restrict mute functionality so that users can only mute or unmute themselves by default, along with an option to disable the “muteParticipant” capability through roles or permissions. Additionally, the UI Kit should support conditionally hiding or disabling mute controls for other participants based on these permissions, while still allowing flexibility for privileged roles such as moderators or admins to retain this capability if required.
The expected outcome is that each participant can manage only their own microphone unless explicitly granted additional permissions. Muting others would be restricted by default, and the UI Kit would dynamically reflect these permission settings.
Implementing this feature would significantly improve user experience, prevent misuse, align CometChat with standard practices in modern communication platforms, and reduce the need for extensive UI-level customizations.
Please authenticate to join the conversation.
New
💡 Feature Request
Get notified by email when there are changes.
New
💡 Feature Request
Get notified by email when there are changes.