Custom Lists are another new feature that allows you to create flexible registrant segments independent of ticket types. Unlike Ticket Type Lists, registrants can belong to multiple Custom Lists simultaneously.
Priority: Custom Lists are ranked by Priority.
The list higher in the table takes precedence when permissions conflict.
You can drag lists to reorder them and adjust their priority.
Name: Name of the custom list
Registrants: The number of registrants assigned to the custom list.
Permission: About the rules/permission overview
Action: Allows you to delete the list.
Clicking on a specific list name (e.g., "VIP-Virtual") will take you to its management interface. Here, you will find four primary tabs: Registrants, Permissions & access, Automations, and Settings.
The Registrants Tab
This tab allows you to view and manage the attendees assigned to this Custom List.
Search: Use the search bar to filter members by name, email address, company name, or title.
Add Registrants: Use the + Add registrants button to manually add attendees to this list.
Viewing Members: The table displays the Registrant's name, their Ticket Type (to help you understand their primary classification), their Status, and Actions.\
Permissions & access
The Permissions & access tab for Custom Lists provides granular control over what attendees can see and do. Understanding how permissions resolve across multiple lists is important.
Automations
The Automations tab lets you keep a Custom List filled automatically. Instead of adding and removing registrants by hand, you define a set of conditions, and Brella manages the list membership for you as registrants meet — or stop meeting — those conditions.
Note: Automations are available for Custom Lists only. They are not available for Ticket Type Lists.
How automations work
Automations are built from conditions and condition groups.
A condition is a single rule, such as Accepted meetings is at least 1.
A condition group holds one or more conditions.
Within a group, you choose how its conditions combine:
Match ALL — the registrant must meet every condition in the group.
Match ANY — the registrant must meet at least one condition in the group.
Across groups, every group must match. When you add more than one condition group, a registrant has to satisfy all of them to be on the list.
An example
Say you set up three groups:
Match ANY: Accepted meetings is at least 1 or Pending meetings is fewer than 3
Match ALL: Registrant status is Joined
Match ALL: Accepted hosted buyer meetings is at least 1
Brella reads this as:
Add everyone with at least 1 accepted meeting or fewer than 3 pending meetings, and with status Joined, and with at least 1 accepted hosted buyer meeting.
A registrant has to satisfy all three groups to be added to the list.
Registrants are added and removed automatically as they start or stop meeting your conditions — no manual updates needed.
Available conditions
You can build automations from a wide range of event data. Conditions are grouped by area:
Sessions
Bookmarked (a specific) session
RSVP'd to (a specific) session
Sessions RSVP'd [count]
Session ratings given [count]
Networking
Accepted meetings [count]
Pending meetings [count]
Rescheduled meetings [count]
Rejected meetings [count]
Accepted hosted buyer meetings [count]
Rescheduled hosted buyer meetings [count]
Meeting ratings given [count]
Pending chats [count]
Accepted chats [count]
Lead scans received [count]
Note: Only counts if the registrant was scanned by a sponsor rep.
Lead scans performed [count]
Note: Only counts if the registrant is a sponsor rep and scanned a lead.
Times reported or blocked [count]
Status
Registrant status (for example, invited or joined)
Sponsors
Rep for (specific) sponsor
Visited (specific) sponsor booth
Custom fields
Custom field value
Additional conditions may be available depending on how your event is configured. This conditions list is subject to change at Brella's discretion.
Saving an automation
Once your conditions are set up, click Save automations.
Brella immediately checks every registrant and adds anyone who matches to the Custom List. From then on, the list keeps itself up to date as attendee activity changes throughout the event:
A registrant who meets the conditions is added automatically.
If they later stop meeting the conditions, they are removed automatically.
If they meet the conditions again, they are added back automatically.
This keeps your Custom Lists accurate without any manual upkeep.
Excluding registrants
Sometimes you'll want to keep a specific registrant off a list, even though they match your conditions. That's what Exclusions are for.
When you exclude a registrant, they're removed from the list and automations won't add them back — even if they still match the conditions.
To exclude a registrant:
Open the Registrants tab.
Find the registrant you want to exclude.
Click Remove from list.
The registrant is removed from the Custom List and added to its Exclusions list. They stay out until you remove them from Exclusions.
You can also add registrants to the Exclusions list directly from the Automations tab.
Tip: Exclusions let you handle one-off exceptions without changing your automation rules.
A note on manual changes
Anything you do by hand takes priority over automations:
Manually added registrants stay on the list. Automations won't remove them, even if they don't match your conditions. To take them off, remove them yourself.
Excluded registrants stay off the list. Automations won't add them back until you remove them from Exclusions.
Settings
This tab contains the core configuration and metadata for your Custom List.
General Settings:
List Name: The internal name for the list (e.g., VIP-Virtual).
Description: Internal notes visible only in the Admin Panel.
List ID: A unique system ID (e.g., 16172)
Danger Zone:
Delete this list: Allows you to delete the Custom List.
Note: Registrants stay in the event — they are just removed from this specific list.