# Best Pattern for Grant/Revoke access by controlling client

**URL:** <https://community.wowza.com/t/best-pattern-for-grant-revoke-access-by-controlling-client/55250>\
**Category:** Wowza Video (Formerly Streaming Cloud)\
**Created:** [May 25, 2020, 10:45pm UTC](https://community.wowza.com/t/best-pattern-for-grant-revoke-access-by-controlling-client/55250 "2020-05-25T22:45:17Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Robert\_Blackburn](https://avatars.discourse-cdn.com/v4/letter/r/4da419/32.png) [@Robert\_Blackburn](https://community.wowza.com/u/Robert_Blackburn)\
**Post date:** [May 25, 2020, 10:45pm UTC](https://community.wowza.com/t/best-pattern-for-grant-revoke-access-by-controlling-client/55250/1 "2020-05-25T22:45:17Z")

</div>

We need to use Wowza Streaming Cloud for our solution, ideally using the REST API.

We need to allow client A to grant client B permission to live stream. Once granted client B will them be prompted to send video/audio via WebRTC, which will be viewed by Client A (and potentially 1 other viewer). Client B also receives audio/video from Client A. Client A can then revoke access to Client B, and potentially grant it to Client C. Once revoked, client B needs to loose all access to the stream.

Is the typical approach here to use the API to create a new Live Stream each time and push the new stream’s information to client when access is granted, then delete the steam when client A revokes access. Or is there a cleaner design pattern for this?