Google Meet host settings

Last updated: September 16, 2026

By default, whoever organises an interview is also who Google Meet treats as its host. Kula lets you change that — pick a different Meet host for an interview, so the person actually running the room (not just whoever booked it) has host controls.

Who can do this: Recruiter, Hiring Manager, Admin, Super Admin can choose a host when scheduling. Granting the permission that lets someone be chosen as host is done by that person themselves, on their own account.

Where to find it: Grant the permission under Settings → Integrations (Google Calendar card). Choose a host wherever you schedule a Google Meet interview — a single schedule, an interview plan's default, or Schedule All.

Why this matters:

Google Meet's own access settings

Google Meet itself has three access settings that control who can get into a call without waiting:

  1. Anyone can join using the link — no host needs to admit anyone.

  2. Anyone with access to the interview can join — participants get in freely even with a host set.

  3. The host must let participants in — only the selected host can admit everyone else.

With the first two settings, who's marked as host doesn't really change anything — everyone can join regardless. It's the third setting where host selection matters. Before this feature existed, Kula always set the recruiter as host for every Google Meet interview — so on an account with that Google Meet setting turned on, an interviewer or candidate could get stuck waiting in the lobby until the recruiter personally joined and let them in, even when the recruiter wasn't otherwise part of the conversation. That's a Google Meet-level restriction, not something Kula controlled.

Host selection is the fix: you can now choose the recruiter or an interviewer as host, so whoever actually needs to admit people into the call can be the one who's able to — instead of everything routing through the recruiter by default.

Grant the Google Meet host permission

Before someone can be picked as a host, they need to grant Kula an extra Google permission:

  1. Go to Settings → Integrations.

  2. On the Google Calendar card, click Re-authenticate.

  3. Approve the additional permission when Google prompts for it.

Until this is granted, that person still shows up in the Host dropdown, but disabled, with an "Action needed" tag — hovering explains they need to connect or refresh their Google Calendar connection to host Meet interviews.

Set a default host on the interview plan

An interview plan can prefill who hosts — organiser or interviewer — so every interview scheduled from that plan picks up the same default automatically, without you choosing it each time.

Choose a host when scheduling

  • Scheduling one interview: once Location is set to Google Meet, a Host dropdown appears — pick from the interviewers on that interview, or the person scheduling it.

  • Schedule All: a Host column appears per interview in the bulk-scheduling flow, so you can set the host for each one before confirming the batch.

  • Whichever location isn't Google Meet, no Host field appears at all — this only applies to Meet.

Once you confirm, Kula creates a host-owned Google Meet space and attaches it to the event — other participants are booked as attendees on the host's event, not the organiser's.

Good to know

  • The host can only be one of the interviewers already on that interview, or the person scheduling it — not an arbitrary person in your organisation.

  • Host selection is required once Google Meet is the location — you can't confirm the schedule without picking one.

  • Ad-hoc interviews default to organiser-hosted, though you can change the host during edit or at schedule time.

  • A self-schedule, one-on-one interview where the actual interviewer isn't decided yet locks the host to the organiser — since Kula can't know who the interviewer will be until the candidate picks a slot, the dropdown is disabled in that case.

  • If the eligibility check itself fails to load, Kula doesn't lock everyone out — every option stays enabled rather than falsely telling every recruiter they need to reconnect a working calendar.

FAQ

  • I'm trying to schedule an interview with several people and it says I can't host all of them — what's going on?

    You can still schedule the interview as usual — by default, whoever's scheduling it is preselected as the host, so nothing's blocking you. If you specifically want someone else to be the host instead, that person needs to re-authenticate their Google Calendar connection first: hosting on someone else's behalf requires a permission that only they can grant, not something a recruiter can set up on their behalf.

Need help?

If you have questions or need assistance, reach out to us at support@kula.ai or use the in-app chat.