Group event scheduling and capacity

Short answer: Allow several invitees to reserve the same session. Begin with “Set the session duration, location, and maximum participant capacity.” and verify the result through the public participant path.

Before you change the setup

Identify the exact organizer, event type, public link, and time zone involved before editing anything. Save the current behavior or take a screenshot so the test has a reliable before-and-after comparison.

How to complete this task

Set the session duration, location, and maximum participant capacity.Start with the intended outcome and the record that controls it.
Explain whether guests can see one another or only the organizer.Review every related setting before saving so one rule does not mask another.
Book until capacity is reached and confirm the slot closes.Keep private data and guest-facing information clearly separated.
Cancel one test attendee and verify the place reopens.Complete the same path an external participant will use.

Verify the participant result

Run one successful case and one edge case. Confirm the public title, local time, available choices, duration, location, confirmation, calendar file, and private management path as applicable. Then check the organizer view and any email delivery record. A saved setting is not proof that the scheduling lifecycle worked.

Troubleshoot group event scheduling

These are the failures reported most often for this specific task, with the cause that explains each one.

The session did not close at capacity.

Verify the maximum is set on the event rather than assumed. Book up to the limit in a test to confirm the slot closes.

Attendees can see each other's details.

Decide deliberately whether the guest list is visible. For external sessions it usually should not be.

A cancellation did not free a place.

Cancel one test attendee and confirm the count decreases and the place reopens before running a real session.

Related Meetin.gs help

Return to the Meetin.gs Help Center for the adjacent configuration guide, or send the exact event code and expected result when the documented checks do not explain the behavior.

Group event scheduling and capacity acceptance checklist

Use the following evidence map while completing this specific task. It ties each action to an observable result so another person can repeat the setup or diagnose it without guessing.

1. Set the session duration, location, and maximum participant capacity.

Write down the intended result, the organizer or account that owns it, and the exact event type or public link in scope. This prevents a correct change from being applied to the wrong record.

2. Explain whether guests can see one another or only the organizer.

Inspect the related rules and dependencies before saving. Record the previous value and the new value, including the time zone, provider account, or team owner when one controls the outcome.

3. Book until capacity is reached and confirm the slot closes.

Review what an invitee can see and what remains private. Keep only the context needed to complete the meeting task, and make the fallback understandable when information is missing.

4. Cancel one test attendee and verify the place reopens.

Complete this step from a signed-out participant session. Preserve the resulting URL or event code, displayed state, message, calendar output, and any provider response needed to prove the task worked.

Evidence type	What to record
Controlling input	The account, event type, setting, public link, and time zone used in the test.
Participant result	The exact choices, context, confirmation, or error visible while signed out.
Lifecycle result	What changes after confirmation, finalization, cancellation, reschedule, or retry.
Failure boundary	The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.
Owner	The person responsible for correcting the setting, provider connection, content, or customer communication.

Evidence type

What to record

Controlling input

The account, event type, setting, public link, and time zone used in the test.

Participant result

The exact choices, context, confirmation, or error visible while signed out.

Lifecycle result

What changes after confirmation, finalization, cancellation, reschedule, or retry.

Failure boundary

The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.

Owner

The person responsible for correcting the setting, provider connection, content, or customer communication.

RELATED CAPABILITY

Team scheduling

Support collective hosts, pooled availability, group sessions, and fair round-robin distribution. This page explains team scheduling requirements. Confirm production availability before depending on this capability.

Review scope

Group event scheduling and capacity: frequently asked questions

Short answers to the questions organizers ask most about group event scheduling.

What is a group event?

One session that several participants book into, such as a webinar, class, or office hour, with a capacity limit rather than a single reservation.

How does capacity work?

Each booking consumes a place, and the slot closes once the maximum is reached. Test this by booking up to the limit before running a real session.

Can attendees see each other?

That is your decision, and it should be deliberate. For external sessions the guest list usually should not be visible.

What happens when someone cancels?

The place reopens and the count decreases. Verify this with a test cancellation before you rely on a waitlist or a full session.