Why internal events want sign-in
For an external webinar, asking guests for a first name and email at the door is exactly right. For an internal all-hands, it is a small irritation repeated across the whole company, and it produces a list of typed names and personal addresses that someone then has to match to the staff directory.
Sign-in fixes both problems. Employees arrive already known, so the door opens without a form, and the attendee list shows the people who actually came, under the identities your company already manages. For communications leaders that means a reliable answer to who heard the message. For people teams running onboarding or required sessions, it means attendance that lines up with records. And for sensitive briefings, it means the room page only opens for people your company has said may enter.
What single sign-on covers, and what it does not
Being precise here prevents a false sense of security, so we spell it out in every scope.
- Covers: who may open the room page. Employees sign in with the company login before they reach the waiting room, and the room records them by that identity.
- Covers, as scoped: which groups may enter which rooms, and how hosts and room owners sign in to manage rooms.
- Does not cover: the meeting itself. The meeting platform's passcode and settings still apply, and the meeting licence is still the capacity cap.
- Does not cover: the raw meeting link. Anyone who has the platform's own link can join through the desktop app and bypass the room, so keep that link out of circulation for internal-only events.
Questions your IT team will ask
Sign-in touches identity, so IT will want answers early. These are the questions a single sign-on scope works through, and it helps to have an owner for each one before the first call.
- Which identity provider and sign-in standard does the company use, and who administers it?
- Which employees or groups may enter each room, and are contractors or partners included?
- Do outside guests attend some internal events, and should they use the normal guest door instead?
- What should happen when sign-in fails on the day: a retry, a helpdesk message, or the guest door?
- Which details from the sign-in should the room keep for the attendee list, and nothing more?
- Who signs off the setup, and which event will act as the pilot?
Designing the door for mixed audiences
Many internal events are not purely internal. A sales kickoff might include partners, a town hall might include board members, and a training session might include new hires whose accounts are not ready yet. Decide the policy room by room rather than once for the whole company. One pattern works well: an internal room that requires the company login, and a separate guest room with the normal first-name-and-email door for outside audiences. Each room then has one clear rule, and nobody has to guess which door to use.
Whatever you choose, write the rule on the invitation. If employees should use the company login, say so in the email and in the waiting-room message, and name who to contact if sign-in does not work.
Running a signed-in event on the day
The run-of-show barely changes. Open the room early so employees can sign in and wait in the branded lobby with the countdown running. Keep a backup host signed in on a second device, and have someone from IT or the helpdesk on standby for the first ten minutes, which is when sign-in questions arrive. Start the meeting in the meeting app as host, then press Start the room, and every waiting employee moves into the meeting together, joined muted. After the event, the attendee list reflects signed-in identities, ready for whatever follow-up your comms or people team planned.
Test the whole flow before the first real event with a handful of colleagues from different teams, devices and networks. Sign-in problems almost always show up in a test, and almost never need to show up in front of the whole company.
Common pitfalls, and how to avoid them
Most sign-in trouble on event day comes from a short list of avoidable causes, and each one has a simple countermeasure.
- Sharing the raw meeting link alongside the room link. People pick the one they recognise, and anyone on the raw link bypasses the room. Send the room link only.
- Forgetting new starters. Accounts for people who joined this week may not be ready; give them the guest door or a named contact.
- Testing only from the office network. Test from home networks, phones and personal browsers too, because that is where employees will be.
- Letting the waiting room stay silent. Put the sign-in instruction and a helpdesk contact in the waiting-room message, so a stuck employee knows what to do.
- Treating sign-in as capacity planning. It decides who may enter, not how many can; the meeting licence still sets the participant limit, and the room warns you as attendance approaches it.
Getting started
Single sign-on is scoped on request, often alongside multi-room administration and white-label, and quoted with no published price. Bring your IT contact to the first call with the answers above, and our team will propose a scope and a quote, including a pilot event in one room before a wider rollout.
If you are not ready for sign-in yet, you can start a free 30-day trial, no card, and run internal events in a Branded Room or Custom Deluxe today with the first-name-and-email door, and move to company sign-in once the pilot has shown what your internal audience needs.