Overview
Roles in a Meeting Program define who can request meetings with whom. The Roles Settings screen in the Admin Panel is where the organiser declares the roles in the program (for example Buyer and Seller) and the matchmaking rules between them.
Getting roles right is the single most important step in setting up a Meeting Program — the rest of the program (lists, schedule, tables) is shaped by what is configured here.
Opening Roles Settings
From the Meeting Program page, open Settings, then Roles.
Defining roles
Add one role per participant type the program needs. Common patterns include:
-
Buyer / Seller — a classic two-sided program where one side requests and the other accepts.
-
Participant — a single-sided program where any participant can request meetings with any other participant.
-
Multi-sided — a program with three or more roles (for example Buyer, Seller, Press, Speaker) with different matchmaking rules between each pair.
For each role configure:
-
Role name — what the role is called in the Admin Panel and on the frontend.
-
Source audience — which event users are eligible to take this role (typically driven by their user type or category).
-
Visibility — whether participants with this role are shown to others, and to which other roles.
Matchmaking rules between roles
For every pair of roles, configure who can request meetings with whom:
-
One-way — only one side can initiate, the other only responds (typical Buyer → Seller).
-
Two-way — either side can initiate.
-
No matchmaking — the two roles do not meet within this program.
Where appropriate, additional per-pair rules apply — for example a cap on how many meetings of that type any one participant may have.
Timing
Lock the role configuration before opening the booking window. Changing roles after participants have started requesting meetings can invalidate in-flight requests and is not advised.