> ## Documentation Index
> Fetch the complete documentation index at: https://help.pipelime.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Meetings overview

> Your company meeting portal, individual Meeting Links, Bookings, and the calendar connections that make slots real.

export const UiPath = ({children}) => {
  const parts = String(children).split(/\s*(?:→|>)\s*/).filter(Boolean);
  return <span className="pl-path">
      {parts.map((part, index) => <span key={`${index}-${part}`}>
          {index > 0 && <span className="pl-path__sep">→</span>}
          {part}
        </span>)}
    </span>;
};

export const Screenshot = ({id, alt, caption, frame = 'browser', url, marks = [], lang = 'en', workspace = 'northwind-outbound'}) => {
  const src = `/images/screenshots/${lang}/${id}.png`;
  const chrome = url ? `app.pipelime.ai/${workspace}${url}` : 'app.pipelime.ai';
  return <figure className={`pl-shot pl-shot--${frame} not-prose`}>
      <div className="pl-shot__frame">
        {frame !== 'bare' && <div className="pl-shot__bar">
            <span className="pl-shot__dots">
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
            </span>
            <span className="pl-shot__url">{chrome}</span>
          </div>}
        <div className="pl-shot__media">
          <img src={src} alt={alt} loading="lazy" />
          {marks.map(mark => <span key={mark.n} className="pl-shot__mark" style={{
    left: `${mark.x}%`,
    top: `${mark.y}%`
  }} aria-hidden="true">
              {mark.n}
            </span>)}
        </div>
      </div>
      {caption && <figcaption className="pl-shot__caption">{caption}</figcaption>}
    </figure>;
};

Meetings covers three surfaces: the links you create, the bookings they produce, and the pages an invitee opens when they use one. This page says where each of them lives.

<div className="pl-availability">
  <div className="pl-availability__row">
    <div className="pl-availability__label">Where</div>
    <div className="pl-availability__value"><span className="pl-path">Meetings<span className="pl-path__sep">→</span>Meeting Links</span></div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">Your role needs</div>
    <div className="pl-availability__value">Read access to Meeting Links <code>read-meeting-links</code>. Admin, Member and Viewer have it by default.</div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">To create or change</div>
    <div className="pl-availability__value"><code>create-meeting-links</code> to add one, <code>update-meeting-links</code> to change one, on top of the permission above.</div>
  </div>

  <div className="pl-availability__note">If you cannot find this in your sidebar, your workspace may have a custom menu configuration. Contact support and we will check it for you.</div>
</div>

## Whether Meetings is in your sidebar at all

**Meetings** sits behind a switch that is set when the app is built, and it is switched off in the app as it ships. The switch is on the group rather than on the rows inside it, so **Meeting Links** and **Bookings** arrive and disappear together. You never get one without the other.

## Meeting Links

Open <UiPath>Meetings → Meeting Links</UiPath> and the **Company Meeting Link** banner is the first thing on the page (1). It is one address for the whole workspace, and the banner says what sits behind it: a meeting portal where visitors explore and book from your available meeting types, rather than a page for one of them. **Copy link** puts that address on your clipboard, and **Create new link** sits beside it.

Under the banner, Individual Meeting Links lists one card per meeting type, with its own New meeting link button in the corner. Both buttons do the same thing, and neither opens a blank form. [Creating a link](/en/meetings/create-a-meeting-link) saves a real, working one the moment you click. Where a role cannot create links, both buttons are simply absent; there is no greyed-out control explaining itself.

### What a card shows

Each card leads with the link's name, then a chip for its duration and a **Video** chip. Under a divider comes its description, or *No description available.* when it has none, and, once its numbers arrive, a line of views, bookings and a conversion rate, which reads as a dash until the link has been viewed at least once. The footer carries the hosts as an avatar group, or a **No hosts** chip when nobody is assigned, alongside five actions: **Copy link**, **Share / Embed**, **Preview**, **Edit** and **Delete**. **Edit** and **Delete** hang off `update-meeting-links` and `delete-meeting-links`, which are separate permissions. They can be missing from a card whose other three actions are there.

Above the chips (2), a card says whether a calendar sits behind the link. With one, a green **Calendar connected** line. Without one, an amber **Calendar integration required for booking**. A link created from this page starts without a calendar, so that warning is what a new link shows until you connect one from the link's own settings.

<Screenshot id="meetings/overview--links-list" url="/meeting-links" alt="The Meeting Links page: the Company Meeting Link banner with Copy link and Create new link, and three cards below: Intro call, Product demo and Quarterly review, each carrying an amber Calendar integration required for booking warning above its chips" caption="None of these three links has a calendar behind it, so every card carries the same warning." marks={[{ n: 1, x: 50, y: 14 }, { n: 2, x: 20, y: 44 }]} />

With no links at all, only the row of cards changes. It gives way to a single box, while the banner above it and the Individual Meeting Links header stay exactly where they were.

<Screenshot id="meetings/overview--empty" url="/meeting-links" workspace="acme-labs" alt="The Meeting Links page with no links yet: the Company Meeting Link banner and the Individual Meeting Links header both still showing at the top, and below them a dashed box with a calendar icon, the heading No meeting links yet, and a button to create the first one" caption="The banner does not react to having no links. It still offers the portal address, and the corner button is still the way to make the first one." />

## Bookings

**Bookings** sits next to **Meeting Links** in the sidebar and asks for nothing extra: it is behind the same `read-meeting-links` permission the list page is. It is where every meeting booked through any of your links ends up. See [manage bookings](/en/meetings/bookings) for what you can do to one from there.

## What an invitee sees

The portal and each link's own page are a separate surface: they render on the meetings subdomain, a different address from the app you work in. **Preview** on a card is the shortcut to one: it opens that link's page in a new tab. [What invitees see](/en/meetings/what-invitees-see) walks through that side from the invitee's end.

## Related

<CardGroup cols={2}>
  <Card title="Create a meeting link" icon="calendar-plus" href="/en/meetings/create-a-meeting-link">
    New meeting link creates a working 30-minute link straight away. Then you rename it, set its URL and pick who hosts it.
  </Card>

  <Card title="Manage bookings" icon="calendar-check" href="/en/meetings/bookings">
    Every meeting booked through your links in one table: join, reschedule, reassign the host, cancel or mark a no-show.
  </Card>

  <Card title="What invitees see" icon="external-link" href="/en/meetings/what-invitees-see">
    The portal, the calendar, the details form and the confirmation, plus the page an invitee uses to reschedule or cancel.
  </Card>

  <Card title="Calendar connections" icon="calendar" href="/en/workspaces-account/calendar-connections">
    Connect, reconnect or disconnect a calendar, and choose which calendars are checked for conflicts and where bookings are created.
  </Card>
</CardGroup>