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

# Participant types and rules

> Reference for the Participant types tab: adding types, Selectable at registration, participant type rules, and when a type can't be deleted.

The **Participant types** tab in **Event settings** defines the groups at your event, such as Buyer and Seller, and the rules between them. Each participant belongs to one type, and an event needs at least one type before it can be published. The tab ends with [profile fields](/host/settings/profile-fields), which have their own page.

## Participant types

Select **Add participant type** to open the dialog, then **Save changes**.

| Control | What it does | Limits |
| - | - | - |
| **Name** | Shown with the type's color wherever the console lists participants. | Required, up to 255 characters. |
| **Color** | Choose one of nine presets, or set your own with the color area, the **Hue** slider, or a hex value. | |
| **Selectable at registration** | Lets people registering through the public link choose this type. Saves as soon as you switch it. | |
| Row order | Drag a row to reorder the types. | |

Use **Edit participant type** and **Delete participant type** at the end of each row. Deleting a type also removes its participant type rules, its custom meeting limits, and its profile field assignments. A type with participants assigned, a type that a profile field applies to exclusively, and the last type of a published event can't be deleted. When an exclusive field exists, the dialog names it and disables the delete button. Change that field's **Applies to** first.

## Participant type rules

Rules are directional. Select the **Requester** type at the top, then set the switches on the card of each type it can interact with, including its own. Buyer → Seller and Seller → Buyer are separate rules, so set both.

| Switch | When on | Default |
| - | - | - |
| **Participant list visibility** | The requester type sees this type in the participant list. | On |
| **Meeting requests** | The requester type can send meeting requests to this type. Shown on the Meet & AI plan. | On |
| **Messages** | The requester type can message this type. | On |

Switches save immediately. If visibility is off but meeting requests are on, the card warns that participants can request meetings with people they can't see in the participant list.

## Effects elsewhere

* A **Public link** event needs at least one type with **Selectable at registration** on. Otherwise the [Registration](/host/settings/registration) tab warns that no one can register through the link.
* Meeting limits per type are set in [Meeting rules](/host/settings/meeting-rules).

## Troubleshooting

<AccordionGroup>
  <Accordion title="Delete participant type is disabled">
    A profile field applies only to this type, and the dialog names it. Open the
    field under **Profile fields**, change **Applies to**, then delete the type.
  </Accordion>

  <Accordion title="No one can register through the link">
    The event uses a public link, but no type is selectable. Turn on
    **Selectable at registration** for at least one type.
  </Accordion>
</AccordionGroup>


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