Meeting availability settings

Short answer: Set working hours, booking windows, buffers, notice, and overrides. Begin with “Set ordinary working windows in the organizer's local time zone.” 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 ordinary working windows in the organizer's local time zone.Start with the intended outcome and the record that controls it.
Add minimum notice, booking horizon, buffers, and a daily cap.Review every related setting before saving so one rule does not mask another.
Create date-specific overrides for leave, travel, or special hours.Keep private data and guest-facing information clearly separated.
Inspect several future weeks as a guest, including a zone change.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 meeting availability settings

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

Slots appear that I cannot actually attend.

Working hours are set but a conflict source is missing. List every calendar that should block time, then re-check a week you know is busy.

No times appear at all for the next few days.

Minimum notice is hiding them. A 48-hour notice rule on a Friday can push the first bookable slot into the following week, which looks identical to an empty calendar.

Availability is right this week and wrong next month.

Check the booking horizon and any date-specific overrides. A horizon that ends mid-month produces exactly this pattern.

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.

Meeting availability settings 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 ordinary working windows in the organizer's local time zone.

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. Add minimum notice, booking horizon, buffers, and a daily cap.

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. Create date-specific overrides for leave, travel, or special hours.

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. Inspect several future weeks as a guest, including a zone change.

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

Customizable availability

Control working hours, booking windows, buffers, daily limits, minimum notice, and date-specific overrides. This page explains customizable availability requirements. Confirm production availability before depending on this capability.

Review scope

Meeting availability settings: frequently asked questions

Short answers to the questions organizers ask most about meeting availability settings.

Why can people book times I am not free?

A conflict source is missing. Working hours define when you could meet; connected calendars define when you actually can. Both are needed.

What is minimum notice used for?

It is the shortest gap allowed between now and a new booking, so nobody can drop a meeting into your next hour. Four hours suits most calls; 24 to 48 hours suits meetings that need preparation.

What are buffers?

Protected time before or after a meeting for travel, preparation, or notes. Buffers block your calendar without changing the duration the invitee sees.

How far ahead should bookings be allowed?

Two to four weeks for most work. A longer horizon invites bookings you cannot yet plan around and produces more rescheduling.