Custom lists group registrants on top of their ticket type list. A registrant can be on many custom lists. Use them to change permissions for a group, or to target content and messages, without changing anyone's ticket type list.
Before you start
You need to be an organization admin or an event admin.
To create a list, see Organize registrants with ticket type lists and custom lists.
Permissions set on a custom list override the ticket type list. When two custom lists set the same permission, the one with the higher priority wins. See How permissions work when someone is on several lists.
Warning: Deleting a custom list can't be undone. Content limited only to that list becomes available to everyone, except featured tiles, which become hidden from everyone.
Where to find it
People > Lists > Custom > select the list name in the admin panel. The list has four tabs: Members, Permissions & access, Automations and Settings.
The header shows Custom list, the list name, the description and the number of members. It also shows the attendance type, the priority ("Priority 2 of 5 custom lists") and the list ID with a copy button.
The Members tab
The table shows Member (name and email address), Ticket type, Status (Joined or Invited) and Actions. Search by name, email address, company name or title. Select a name to open the registrant.
The table does not show whether a member was added by hand or by an automation.
Add members
On the Members tab, select Add members. The Add members panel lists every registrant of the event with their ticket type list.
Search for and select the registrants.
Select Add N members.
The message "Registrants added" confirms it. There is no confirmation step.
People you add here are manual members. Automations never remove them. If someone was already on the list through an automation, adding them here makes them a manual member.
If the person is in the list's Exclusions, adding them removes the exclusion.
You can also add members with the
custom_list_idscolumn of a CSV import, or let the Automations tab add them. A filledcustom_list_idscell replaces the person's hand-added custom lists with the lists in the cell. See Import registrants from a CSV file and Fill a custom list automatically.
Remove members
On the Members tab, do one of these:
For one person, select the ⋮ button in the Actions column, then Remove from list.
For several, select their checkboxes. The table header changes to "N members selected". Select Remove from list.
Read the confirmation. It says the person is removed and added to the list's Exclusions, "so they won't be automatically re-added".
Select Remove and exclude.
The message "Registrants removed" confirms it. The person stays in the event and on their ticket type list.
Removing always adds the person to Exclusions, even if the list has no automations yet. If you set up automations later, excluded people are not added. To let automations add someone again, remove the exclusion on the Automations tab. See Fill a custom list automatically.
Set the priority
The priority decides which custom list wins when two of a person's custom lists set the same permission. #1 is the highest.
In People > Lists > Custom, drag a row by its handle in the Priority column. The message "Custom list moved" confirms it. Dragging works within the current page; show more rows per page to move a list further.
Or open the list's Settings tab and enter a number in Priority order, from 1 to the number of custom lists. Press Enter or leave the field to save.
New custom lists go to the bottom of the order. A new priority takes effect at once for members who are on several custom lists.
Fill the list automatically
The Automations tab adds registrants who match conditions you set and removes them when they stop matching. Conditions include a number of accepted meetings, a session RSVP or a custom field answer. See Fill a custom list automatically.
Change the list settings
Open the Settings tab. Text fields save when you leave them. Attendance type saves when you choose a value. The message "Saved" confirms each change.
Setting | What it does | Default |
List name | The name in the admin panel. Up to 45 characters, unique in the event. Attendees never see custom list names. | The name you entered |
Description | "This is only shown in the Admin Panel". Up to 120 characters. | Empty |
Attendance type | Hybrid events only: In-Person, Virtual or Hybrid. It overrides the ticket type list's attendance type for members, unless a custom list with a higher priority sets another one. | The type chosen at creation |
Priority order | The list's rank among custom lists. | Last |
List ID | The ID to use in the | — |
Custom lists have no Display name.
Delete a custom list
Open the Settings tab.
Under Danger zone, select Delete list.
Read the confirmation, "Members stay in the event — they're just removed from this list.", and select Delete.
You can also select Delete in the Actions column of People > Lists > Custom.
What happens:
Members leave the list and lose its permissions. Their other lists decide instead.
The list's automations and exclusions are deleted.
The list is removed from every session, page, stream, story, announcement and networking area limited to it. Those that were limited only to this list become available to everyone.
A featured tile limited only to this list becomes hidden from everyone. Change the tile's Gating before you delete the list.
Custom emails that targeted only this list have no recipients left.
Other lists that named this list under Specific lists in Allow sending requests to or Allow receiving requests from lose it. If it was the only list named, that setting now blocks all requests.
What attendees see
Attendees don't see custom lists. They see the result: the permissions and the content the list gives them. If the event is in progress, joined attendees whose networking turns on or off because you added, removed or reordered a list get a push notification and an in-app notification.
Troubleshooting
Someone you removed is back on the list
Someone added them again with Add members, a CSV import or the Integration API, or their exclusion was removed. Remove them again.
An automation doesn't add someone who matches
They are in Exclusions, for example because they were removed from the Members tab. Remove the exclusion on the Automations tab. If they are not excluded, the automation has not run since they started matching; the hourly run adds them while the event has not ended.
A permission set on this list doesn't apply to a member
A custom list with a higher priority sets the same permission. Open the member from the Members tab. For joined registrants, the Joined user tab lists their Custom lists with each list's priority. Move this list up, or set the permission to Not set on the other list.