Q: How simple is the onboarding process for people attending an event?

Can everyone in the same room hear each other? Can two people in that room have a private conversation if others are present?

If someone is not behaving properly in a room, can a moderator easily remove them and prevent them from re-entering using their IP address?

What tasks can organizers perform?

What are sub-accounts used for?

With License 3, it says "Participants per live webinar: 600."
Does this mean a maximum of 600 participants can attend the event, regardless of whether they are attending at the same time?
Or does it mean a maximum of 600 participants can attend simultaneously so, for example, up to 900 people could attend a 6-hour event, as long as no more than 600 are present at the same time?

If we buy more than one code, do they add up to increase the number of potential attendees at an event?

thanks

StrategistPLUSAug 6, 2025
Founder Team
Richard_GoBrunch

Richard_GoBrunch

Aug 6, 2025

A: Hey Strategist.

Onboarding is very simple, there's a video here that shows step by step https://www.youtube.com/watch?v=6_2X-VyWpq8

1. Yes, everyone hear each other, but you can add multiple rooms inside the same space if you want to separate them into groups or by topics.

2. Yes, there's an option to Ban under Attendees, Individual Search. Once you hit that button, the person's account and IP is banned for that specific room.

3. Organizers can do a lot, really. Present, share screen, share boards, mute or unmute people individually or all together, give presentation or moderation privileges, move attendees to different rooms, change the background in real time and more.

4. Sub-accounts are suitable for team members, very useful for virtual workspace use cases. Once team members are added as sub-accounts and as moderators, they can help you to manage your rooms.

5. The limit is 600 per room.

6. GoBrunch is license based and Tier 3 is the maximum that you can get.

Share
Helpful?
Log in to join the conversation
Posted: Aug 6, 2025

thanks Richard!