Availability rules decide which times a guest can see. Working hours, minimum notice, a booking horizon, buffers, and a daily cap cover almost every case. The availability page lists them; the rules guide explains sensible defaults.
Before you start
- Know your real working windows in your own time zone.
- Decide how much notice you need before a meeting.
- List any leave or travel dates to add as overrides.
How to complete this task
- Set ordinary working windows in the organizer's local time zone.
- Add minimum notice, booking horizon, buffers, and a daily cap.
- Create date-specific overrides for leave, travel, or special hours.
- Inspect several future weeks as a guest, including a zone change.
Finish by opening the public link in a signed-out browser: a saved setting is not proof that the guest path works.
Troubleshooting
The problems people report most often with this task, and the cause behind 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.
