# Require Participant ID on Dial-in

**URL:** <https://devforum.zoom.us/t/require-participant-id-on-dial-in/118027>\
**Category:** Feature Requests\
**Tags:** phone, video-sdk\
**Created:** [September 24, 2024, 9:35pm UTC](https://devforum.zoom.us/t/require-participant-id-on-dial-in/118027 "2024-09-24T21:35:07Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sam9](https://avatars.discourse-cdn.com/v4/letter/s/858c86/32.png) [@sam9](https://devforum.zoom.us/u/sam9)\
**Post date:** [September 24, 2024, 9:35pm UTC](https://devforum.zoom.us/t/require-participant-id-on-dial-in/118027/1 "2024-09-24T21:35:07Z")

</div>

For videosdk Dial-in on web it would very convenient to have a top level session setting where you can set: requireParticipantIdDialIn or something so that when a participant calls in they can’t bypass the participant ID option. If they bypass the participant ID option we don’t have an ability to link the web user to the phone user that just dialed in because they are essentially anonymous at that point.

This works great right now if the user proceeds to dial in the participant ID but given the optional status of it most are not going to do it…

---

<div class="post-metadata">

**Author:** ![sam9](https://avatars.discourse-cdn.com/v4/letter/s/858c86/32.png) [@sam9](https://devforum.zoom.us/u/sam9)\
**Post date:** [October 14, 2024, 9:50pm UTC](https://devforum.zoom.us/t/require-participant-id-on-dial-in/118027/2 "2024-10-14T21:50:04Z")

</div>

@vic.yang

Appreciate the recent progress on port 443 connections via dial out users and the upcoming add for muteUponStartAudio.

I’m curious on how this require participant ID feature ranks in feasibility as well as importance with you/team. Would be epic to see it in next release but unsure on your thoughts…

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [October 15, 2024, 2:49am UTC](https://devforum.zoom.us/t/require-participant-id-on-dial-in/118027/3 "2024-10-15T02:49:26Z")

</div>

Hey @sam9

Thanks for your feedback.

We have received your feature request and are currently investigating whether it’s feasible to bypass participant ID.

Thanks  
Vic

---

<div class="post-metadata">

**Author:** ![sam9](https://avatars.discourse-cdn.com/v4/letter/s/858c86/32.png) [@sam9](https://devforum.zoom.us/u/sam9)\
**Post date:** [October 15, 2024, 3:51am UTC](https://devforum.zoom.us/t/require-participant-id-on-dial-in/118027/4 "2024-10-15T03:51:20Z")

</div>

Feasible to \*not bypass it.

Basically just looking for a way to require it. Anyways – think that was just a typo.

Thanks!

---

<div class="post-metadata">

**Author:** ![sam9](https://avatars.discourse-cdn.com/v4/letter/s/858c86/32.png) [@sam9](https://devforum.zoom.us/u/sam9)\
**Post date:** [November 9, 2024, 6:12pm UTC](https://devforum.zoom.us/t/require-participant-id-on-dial-in/118027/5 "2024-11-09T18:12:50Z")

</div>

Hey just checking on updates on this. Curious if you found it feasible or not. Let me know if you need any clarifications on anything. Thanks!

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [November 11, 2024, 2:34am UTC](https://devforum.zoom.us/t/require-participant-id-on-dial-in/118027/6 "2024-11-11T02:34:53Z")

</div>

Hey @sam9

There are currently no updates. There is voice guidance in the incoming calls.

Thanks  
Vic
