Luna_Mora proposed making camera and screen sharing permissions granular and role-based, rather than a simple on/off toggle. The goal was to allow moderators to restrict screen sharing to specific roles to prevent inappropriate content from being shared in voice rooms without direct supervision. Falco confirmed the request was for both features to be controlled via site settings based on user groups, similar to existing voice access controls. Luna_Mora agreed, emphasizing the need for separate permissions for camera and screen sharing to avoid an “all or nothing” approach.
Falco announced a prepared Pull Request (#43307) to implement these changes. After the feature was merged, Luna_Mora confirmed that their community successfully implemented the new permissions during a scheduled maintenance window. The feature was tested and found to work exactly as needed, with Luna_Mora expressing gratitude for the improvement. nathank also noted that this addition would be beneficial for communities requiring tighter control over voice rooms.
Throwing this out there for roadmap consideration, but the permission for cameras and screen sharing should be a.) separated and b.) permissions based, rather than a toggle.
Our current discord community is locked down where people can use voice and camera, but screen sharing they have to be given a specific role for. Since a moderator might not be present in the voice call to monitor what is being shared. (Quite memorably, our streaming permission was messed up at one point and I caught a user doing something weird and they ended up getting themselves kicked from the server over it.)
The more granular the control over who can do what is, the better.
Yes exactly!! Just like how the ability to access voice, create rooms and have access to direct calls are already group based. Having that functionality extended to camera and screen sharing (preferably separately, unless camera and screen sharing are intrinsically linked) rather than a toggle checkbox, all or nothing, on or off sort of thing.
We actually launched out of beta before it was merged in so had to wait until our scheduled maintenance window to get the fix. But we tested yesterday and it works great! It’s exactly what we needed, thank you. <3
until then we have to keep the setting off.
It’s exactly what we needed, thank you. <3