> ## 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.

# FAQ

> Short answers to the questions hosts ask most about publishing, payment, plans, invitations, approval, meetings, billing, and what participants need to join.

<AccordionGroup>
  <Accordion title="Why is Publish event disabled?">
    One of the four **Before you publish** items is still open, or you changed
    the **Site address** without saving it. If the event has already ended,
    change **Date and time** in **Basic info** first. See [Publish the event
    page](/host/publishing/publish).
  </Accordion>

  <Accordion title="Why can't I add a payment method?">
    Only admins add or change the payment method, so members see **Ask an admin
    to add a payment method.** instead of the button. The admin chooses the
    billing currency once, **KRW** or **USD**, and saves a card through Stripe.
    The currency can't be changed after that. See [Add a payment
    method](/host/publishing/payment-method).
  </Accordion>

  <Accordion title="What's the difference between the plans, and can I switch back to Chat?">
    **Chat** gives participants the participant list, 1:1 messages, and
    announcements, and **Meet & AI** adds 1:1 meetings. You choose the plan the
    first time you publish, and a Chat event can upgrade later. Once an event
    has been published on Meet & AI, it can't go back to Chat, even after
    unpublishing. See [Plans](/host/concepts/plans).
  </Accordion>

  <Accordion title="Why is Import disabled?">
    The event has no participant type yet. Create one in **Event settings**
    under **Participant types**, then import. See [Add and import
    participants](/host/participants/import).
  </Accordion>

  <Accordion title="Why is Send invitations disabled?">
    Invitations go out from a published event only, not while a previous batch
    is still sending, and not after the event has ended. Drafts show **Publish
    the event to send invitations.** People invited in the last 12 hours and
    people who unsubscribed are left out of a batch, which can make the count
    lower than you expect. See [Send
    invitations](/host/participants/invitations).
  </Accordion>

  <Accordion title="Why did a participant register without approval?">
    **Require approval** covers registrations through the public link only.
    Participants you add or import are approved on the spot and show as **Not
    invited** until you invite them. See
    [Registration](/host/settings/registration).
  </Accordion>

  <Accordion title="Why does nobody appear under Pending approval?">
    Approval applies to public link registrations only. If **Access** is
    **Invite list only**, nobody registers through the link, and participants
    you add or import are approved at once. Check **Access** and **Require
    approval** in the **Registration** tab. See [Approve
    registrations](/host/participants/approval).
  </Accordion>

  <Accordion title="A participant can't see someone in the participant list or can't request a meeting">
    Participant type rules are directional. In **Participant types**, select the
    **Requester** type and check **Participant list visibility** and **Meeting
    requests** for the other type. Approved participants who haven't entered yet
    appear only while **Show participants in the participant list before they
    enter** is on in **Registration**, and a participant at their meeting limit
    can't send or receive new requests. See [Participant types and
    rules](/host/settings/participant-types) and [Meeting
    rules](/host/settings/meeting-rules).
  </Accordion>

  <Accordion title="Why does my direct assignment ignore a participant's availability?">
    Assigning a meeting from **Schedule** checks participant type rules, meeting
    limits, and time overlaps only. It doesn't check the availability
    participants set on the event page or the **Minimum notice**, so a
    participant can end up with a meeting at a time they had blocked. See [How
    meetings work](/host/meetings/how-meetings-work).
  </Accordion>

  <Accordion title="What happens when I cancel or edit a meeting?">
    On a published event, both participants are emailed. A cancellation carries
    your reason as written, and a change notice goes out only when the time or
    location changes. A canceled meeting frees its location and can't be
    restored. See [Meeting list](/host/meetings/list).
  </Accordion>

  <Accordion title="What happens when I delete a participant?">
    **Delete** in the detail sheet can't be undone. For an approved participant
    on a Meet & AI event it also cancels their upcoming meetings and requests,
    and in a published event the other participants are notified. Each email
    address appears once per event, so to fix a typo you delete the participant
    and add them again with the correct address. See
    [Roster](/host/participants/roster).
  </Accordion>

  <Accordion title="Why does Participants on the Billing page differ from Entered on the overview?">
    Billing counts everyone who was approved and had entered at any point during
    the period, including the first 30 free ones. **Entered** on the overview
    counts participants entered as of now. See [Billing](/host/billing).
  </Accordion>

  <Accordion title="When does billing stop after the event?">
    The last billing period ends at the page end. On Chat the page ends with the
    event, and on Meet & AI it ends at the later of the event end and the end of
    the last **Meeting hours**, so extending meeting hours can add a period.
    Unpublishing doesn't end a period. See [Billing](/host/billing) and [Event
    lifecycle](/host/concepts/event-lifecycle).
  </Accordion>

  <Accordion title="What locks when the event ends, and what locks when the page ends?">
    The event end closes adding, importing, approving, and inviting
    participants, and on an event that has been published it locks **Date and
    time** and **Time zone**. Rejecting, deleting, and announcements still work.
    The page end closes new meetings, moves, time changes, **Meeting hours**,
    and plan changes, while canceling meetings stays open. See [Event
    lifecycle](/host/concepts/event-lifecycle).
  </Accordion>

  <Accordion title="What do participants need to join, and who do they ask?">
    Participants need the email address you have for them. Invited participants
    open the link in the invitation email, participants on a public link event
    register from the event page, and both sign in with a code sent to that
    address. Questions about their registration or approval reach you through
    the event page's contact form and email replies, which arrive at the
    **Support email** set in **Basic info**. For the sign-in steps, point them
    to [Join an event](/participant/join).
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.