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

# Participants

> Reference for the Participants tab: who is listed, search and filters, bookmarks, the chips on each row, and the buttons in a participant's detail sheet.

The **Participants** tab lists the other participants in the event. Who you see, and whether you can message them or request a meeting, follows the participant type rules the host set. The number beside the title counts participants matching your search and filters.

## Who is listed

* Approved participants whose participant type your type is allowed to see.
* Only participants who have entered, unless the host chose to list them before they enter.
* Sorted by name. More rows load as you scroll.

## Search and filters

| Control | What it does |
| - | - |
| **Search participants** | Searches name, company, job title, and introduction. |
| **Participant type** | One participant type at a time, or **All**. Only types you can see are offered. |
| Choice-field filters | One per choice field the host marked as a filter. Any checked option within a field matches, and every filtered field must match. |
| **Bookmarked** | Shows only the participants you bookmarked. |
| **Reset** | Clears the type, field, and bookmark filters. |

On narrow screens, the filters collapse into a **Filters** button as you scroll. The sheet applies your choices when you select **Apply**.

When nothing matches, the list shows **No participants to show** with **Try a different search or filter.** Before anyone has entered, it shows **Participants will appear here once they join.** An empty **Bookmarked** view shows **No bookmarks yet**.

## Rows

Each row shows name and participant type, company and job title, the first line of the introduction, and one chip when there is a meeting between you. Selecting a row opens the detail sheet.

| Chip | Meaning |
| - | - |
| **Needs reply** | They sent a request or proposed a new time, and it's your turn to answer. |
| **Confirmed** | A confirmed meeting, with its time. |
| **Arranged by host** | A meeting the host scheduled for you. |
| **Awaiting reply** | Your request is waiting for their answer. |
| **Meeting requests unavailable** | Your participant type can't request meetings with theirs. Shown only while requests are open and you have no meeting together. |

## Detail sheet

The sheet shows the introduction and the profile fields the host made visible, with links last. Meetings between you appear as a strip above the profile and open in [**Meetings**](/participant/meetings).

| Button | When it appears |
| - | - |
| Bookmark icon | Always. Bookmarks are set only here. Without any other button it becomes a full-width **Bookmark** button. |
| **Message** | The host allows messaging between your participant types, or the two of you already have a conversation. |
| **Respond** | A request or new time from them awaits your answer. Opens it in **Meetings**, even after requests have closed. |
| **Request meeting** | Events with meetings (Meet & AI) while requests are open, with no request pending between you. See [Request a meeting](/participant/request-meeting). |

While a request between you is pending, **Request meeting** becomes a disabled **Awaiting reply**. It's also disabled under **The host is arranging meetings** or **Meeting requests unavailable**, shown above the buttons. After requests close, **Meeting requests closed** replaces it and **Message** becomes the main button. Events without meetings (Chat) show no meeting chips, and **Message** is the main button.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Someone I expect isn't listed">
    The host decides which participant types see each other and whether
    participants appear before they enter. Ask the host if you can't find
    someone.
  </Accordion>

  <Accordion title="Request meeting is disabled or missing">
    **Awaiting reply** on the button means a request between you is already
    pending. Otherwise, the line above the buttons names the reason. Events
    without meetings (Chat) offer **Message** instead.
  </Accordion>

  <Accordion title="There is no Message button">
    The host hasn't enabled messaging between your participant types. If they
    message you first, you can still reply.
  </Accordion>
</AccordionGroup>


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