This message was deleted.
# helpdesks
steep-balloon-41261
07/12/2023, 12:28 PMThis message was deleted.
g
gray-photographer-38040
07/12/2023, 2:37 PMthis is how i will solve this issue first give all subscribe participant the "_*subscribed only token*_", after which as the publisher you can update a particular user token to allow canPublishSources [camera, or mic, etc]
so by so doing you have provided priority to your speaker
gray-photographer-38040
07/12/2023, 2:41 PMor another way
during a time a participant is publishing to the room, give him the roomAdmin privilege which will make him a host, then make other publishers have t canPublish, canPublishData privileges, so the Host can then be able to update the token access of the publishers (speakers)
r
rhythmic-pager-68552
07/12/2023, 3:52 PMThanks a lot! Seems like the way to go here 🙂
rhythmic-pager-68552
07/12/2023, 3:55 PMDo you think that this approach is agile enough for a live session? Degrading all tokens privileges every time a varying speaker is publishing?
g
gray-photographer-38040
07/12/2023, 4:11 PMYes,
According to the documentation, token can be updated via the client or via the backend
r
rhythmic-pager-68552
07/12/2023, 4:21 PMOf course, but the question is whether or not it’s a good practice to change privileges this frequently though 🤔
g
gray-photographer-38040
07/12/2023, 4:23 PMIt is a good practice bro
gray-photographer-38040
07/12/2023, 4:25 PMThe Livekit listen for updates, it wont have be a good idea if they didn't introduce that that, for them introducing it in the first place it's a good idea.
Feel free to do that way
🙏🏻 1
2 Views