This message was deleted.

Couldn't you control this through your app itself? I feel like this could be app business logic. This said, from my understanding its you canPublish or you cannot. Currently I don't think there's a way to control per media type. You can read about the grants from this doc: https://docs.livekit.io/concepts/authentication/#video-grant

I already thought that this could be handled on the app-side with some tweaks on the server, but wanted to make sure that this is the only way. Thanks for the reply!

As Pat said, this could be done at the app layer. But I think you bring up a great point.. we can provide more fine-grained enforcement with the permissions layer. I'm thinking it might be good to break it down into

canPublish<source>

where <source> could be camera, microphone, screenshare, screenshare-audio. that way these are enforced on the server side even if a participant uses a different client to overcome the limitations that you've set at the app layer

Wonderful idea @dry-elephant-14928. This could be a great additional feature. More granularity on per permission level could be handy. Id still keep the original one as a global one, but if you don't want the global one, allowing per source type.

yeah, that makes sense. by default they are the same value as

canPublish

, but you may override to anything