> ## Documentation Index > Fetch the complete documentation index at: https://docs.umoh.io/llms.txt > Use this file to discover all available pages before exploring further. # Meeting rules > Reference for the Meeting rules tab: duration, minimum notice, request expiry, per-person limits, and the meeting hours in which meetings can be booked. The **Meeting rules** tab in **Event settings** decides how 1:1 meetings are requested and booked: duration, minimum notice, request expiry, per-person limits, and the hours in which meetings take place. This tab appears for events on the Meet & AI plan. ## Meeting settings | Setting | What it controls | Default | | - | - | - | | **Meeting duration** | Length of every meeting and of the slots participants choose from. At least 5 minutes, in steps of 5. | 20 minutes | | **Minimum notice** | Slots starting sooner than this can't be requested. 0 minutes or more. | 30 minutes | | **Pending request expiry** | How long a request waits for an answer: 1, 2, 3, or 5 days. A request also expires when its meeting time arrives. | 3 days | | **Limit meetings per person** | When on, set **Max meetings per person** (at least 1) and choose **Per day** or **Entire event**. | Off | | **Count pending requests** | When on, requests waiting for an answer count toward the limit along with confirmed meetings. | Off | Select **Save changes** to apply. A participant at the limit can't send new requests, and no one can request a meeting with them. ## Limits by participant type Shown once the event has a participant type. Each type lists the limit it uses. Select **Edit limit** and choose one: * **Event default**: the type follows the limit in **Meeting settings**. * **Unlimited**: no limit for this type, even when the event has one. * **Custom limit**: its own **Max meetings per person**, **Per day** or **Entire event**. **Count pending requests** applies to these limits too. ## Meeting hours Meeting hours are the dates and daily time ranges in which meetings can be booked. Without meeting hours, meetings can be booked at any time during the event period. Select **Add meeting hours** and fill in: | Field | Rule | | - | - | | **Dates** | A date range in the event time zone. The first set defaults to the event period. Dates can't overlap another set of meeting hours. | | **Time ranges** | One or more start–end ranges applied to every date in the set, 09:00–18:00 by default. Ranges can't overlap, and each end time must be later than its start. | Each set can be duplicated, edited, or deleted. Deleting one leaves confirmed meetings and pending requests as they are. Deleting the last set reopens the whole event period. Participants choose meeting times inside these hours only, and their availability on the event page follows the same hours. ### Hours beyond the event end Meeting hours can run past the event's end date. The event page then stays open, and meetings can be booked, until the last meeting hour ends. * Extending past the event is possible only while the event is still running. * On a published event, if the new end crosses into another monthly billing period, the dialog warns you that entered participants are billed for another month. * Once the event has ended, shortening or deleting the hours that keep the page open ends the event page immediately. This can't be undone. * After the event page has ended, meeting hours can't be added or changed. ## Troubleshooting Each date belongs to one set. To add time ranges on a covered date, edit that set, or choose other dates. Ranges in one set can't share any minutes. Merge them, or start the later range where the earlier one ends. A range ending before it starts is rejected too. In **Meeting settings**, the button turns on only after a value changes and every value is valid: duration at least 5 minutes, notice 0 or more, limit at least 1. In the meeting hours dialog, it needs the dates and every time range filled in. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.