If you see Zoom Error Code 3113, the meeting you are trying to schedule or save does not meet a basic security requirement. The fix is typically straightforward: enable a passcode or turn on the Waiting Room for that meeting so Zoom can apply an entry gate.
This guide focuses on Error Code 3113 for Zoom meetings and Zoom webinars. It explains what the code means, why it triggers, and the exact settings that resolve it without adding unnecessary steps.
- Host or scheduler access is usually required to change the meeting’s Security options.
- If settings look locked or unavailable, an account admin may need to adjust defaults for your user or group.
Table of Contents
What Error Code 3113 Means
Error Code 3113 indicates that neither a passcode nor the Waiting Room is enabled for the meeting or webinar you are trying to create or update. Zoom blocks the action until at least one of these entry controls is turned on.✅Source
You will most often see 3113 at the moment you click Save during scheduling, or when you edit an existing meeting and remove security options. Some integrations (calendar add-ins, templates, or automated scheduling) can also surface the same check when they submit settings that omit both passcode and Waiting Room.
Why Error Code 3113 Happens
Zoom uses a simple rule during scheduling: a meeting should have at least one join barrier. If both passcode and Waiting Room are off, the platform prevents the meeting from being created or updated. Many accounts also set defaults so meetings start with a required passcode or Waiting Room, and the code appears when those defaults are manually removed.
Common Triggers You Can Check in Seconds
- You unchecked Passcode and also turned off Waiting Room while editing a scheduled meeting.
- A meeting template or “copy meeting” flow carried over settings with both security toggles disabled.
- You are scheduling on behalf of someone else (scheduling privilege), and their default security requirements differ from yours.
- An integration created the meeting with incomplete security fields, then Zoom validated it during Save.
Fast Fix for Hosts
The fastest resolution is to enable one of the two controls below. Pick the option that fits your workflow, then save the meeting again. When the security requirement is met, 3113 typically disappears immediately.
Option A: Enable a Passcode
- Open the meeting’s Security section.
- Turn on Passcode and confirm a passcode value.
- Save, then share the updated invite details if needed.
This works well when you want a predictable join step and you can distribute a single code to attendees.
Option B: Enable Waiting Room
- Open the meeting’s Security section.
- Enable the Waiting Room toggle.
- Save, then admit participants as they arrive.
This fits sessions where the host wants entry control and can admit participants when ready, using the Waiting Room.
Fix in Zoom Web Portal
If you have access to the Zoom web portal, it is often the most consistent place to adjust meeting security. The labels may differ slightly by account type, yet the Security section is the key area.
- Sign in to the Zoom web portal and open Meetings (or Webinars if applicable).
- Select the meeting you are editing, then choose Edit.
- Locate the Security section.
- Enable Passcode or enable Waiting Room.
- Click Save, then re-check that one security option remains enabled.
If you see security toggles that are enabled but unchangeable, that usually indicates the setting is locked at the account or group level. In that case, change what is available at the meeting level, or ask an admin to adjust the default policy.
Fix in Desktop and Mobile Apps
When you schedule from the Zoom Workplace desktop or mobile app, the same rule applies: do not leave both Passcode and Waiting Room off. Look for a Security area in the scheduler.
- Open the app and start Schedule for a new meeting (or edit an existing scheduled meeting).
- Find the Security section (sometimes shown as toggles near the bottom of the scheduler).
- Enable Passcode or enable Waiting Room.
- Save the meeting and verify that your invite now includes at least one entry control.
Admin Controls and Locks
On managed accounts, administrators can enforce passcodes for all meetings and control whether users can disable Passcode settings. Zoom also allows passcodes to be enabled at the user, group, or account level, and settings can be locked to keep behavior consistent across the organization.✅Source
If you are not an admin, the practical takeaway is simple: when you encounter 3113, make the change at the meeting level (enable Passcode or Waiting Room) and avoid fighting locked defaults. If a required option is unavailable in your scheduler, it usually means an account policy is guiding the choice.
Why Zoom Enforces This Check
Zoom has publicly documented changes that increase default meeting protection, including requiring passcodes and enabling the Waiting Room by default in certain scenarios. These defaults are designed to provide extra privacy and control for meetings and webinars.✅Source
Common Edge Cases
Some scheduling patterns can make 3113 feel inconsistent. These are the cases that most often explain the mismatch between what you expect and what Zoom validates at Save.
- Editing a copied meeting: A copied event may inherit toggles that leave both Passcode and Waiting Room off.
- Using a Personal Meeting ID: PMI meetings can have their own security requirements; verify the passcode rule for PMI and avoid disabling it unintentionally.
- Recurring meetings: Ensure you are editing the correct series settings so the Security choice persists for future occurrences.
- Scheduling for another host: Scheduling privilege can apply the other host’s defaults, even if your own user has different settings.
- Calendar or app integrations: If an add-in generates a meeting with incomplete security fields, open the meeting once in the web portal and confirm at least one option is enabled.
Passcode and Waiting Room Compared
Both options satisfy the 3113 requirement. The practical difference is how participants get admitted. Use the table to match the control to your meeting style without changing your broader workflow.
| Security Option | How Participants Enter | Host Experience | Typical Fit |
|---|---|---|---|
| Passcode | Attendees join with a code (often embedded in the link). | Minimal manual admission; keep the passcode available for anyone who joins by ID. | Large meetings, recurring sessions, or any event where you want a consistent join step. |
| Waiting Room | Attendees wait until admitted by the host or co-host via Waiting Room. | More hands-on admission; you decide when participants enter the room. | Smaller sessions, interviews, training, or meetings where arrival order matters. |
Verify the Fix Without Guesswork
- Open the meeting details and confirm Passcode or Waiting Room is visibly enabled under Security.
- Copy the invitation and check that the passcode appears (or that the meeting indicates a Waiting Room experience).
- Run a quick join test from another device or a private browser session; confirm the join flow matches the enabled security option.
- If you changed security after sending invites, share an updated invite so attendees use the correct join details.
If It Still Appears
If 3113 continues after you enable one option, the issue is often that the change did not save successfully, or your client is not applying the updated setting. These steps stay focused on what can block the new Security state from sticking.
- Re-open the meeting and confirm the toggles remained enabled; do not rely on memory for Passcode or Waiting Room.
- Try the web portal for the final save; it is often the most consistent interface for meeting settings.
- Update or reinstall the app if the scheduler screen is missing security options, or if saving behaves unpredictably; Zoom documents common steps like uninstall/reinstall and using the official download flow.✅Source
A practical sanity check: if you can save the same meeting after enabling Passcode in the web portal, the error is resolved at the account level. Any remaining issues are usually local to the client or an integration flow.
When to Contact Support
If you have enabled Passcode or Waiting Room, verified that the setting remains enabled after saving, and the platform still returns 3113, it is reasonable to contact Zoom Support. Prepare the meeting ID (if available), the exact scheduling method (web portal, desktop app, mobile app, or integration), and the point in the flow where the error appears.✅Source
FAQ
Does Error Code 3113 happen to participants or to the host?
3113 most commonly appears while scheduling or editing, so it is typically a host-side or scheduler-side message. Participants usually encounter different prompts, such as entering a passcode or waiting in a Waiting Room, after the meeting is created correctly.
If I enable a passcode, do I need to resend the invitation?
It depends on what attendees already received. If you previously sent an invite without a passcode, send the updated details so joining is smooth. If the join link already embeds the passcode, many participants will not need to type it, yet the invite should still reflect the correct Security state.
Which option should I choose: passcode or Waiting Room?
Choose based on how you want to manage entry. A passcode is simpler for recurring or larger meetings where you prefer a predictable join step. The Waiting Room provides tighter control for sessions where the host wants to admit participants intentionally, using a live admission flow.
Why are the security options gray or locked in my account?
That usually indicates an admin policy is enforcing default security behavior. In many organizations, admins require a passcode for all meetings, or they limit the ability to disable specific Security settings. In that situation, enable what you can at the meeting level and request admin assistance if the setting you need is unavailable.
Can enabling Waiting Room change how “Join Before Host” behaves?
Yes, in many configurations, a Waiting Room changes the arrival experience because participants wait for admission. If your meeting relies on attendees joining immediately, a passcode often preserves a more direct join flow while still meeting the 3113 security requirement.
What should I do if an integration keeps creating meetings that trigger 3113?
First, confirm your account defaults apply a passcode or Waiting Room. Then test scheduling once in the web portal to validate the settings save properly. If the integration still produces meetings without either control, update the integration’s meeting template so it always includes a passcode or Waiting Room.