Add Group/Seating Notes to column options in Events
I use this for special seating requests, to indicate organization affiliation, etc. It would be extremely helpful to see this prior to assigning seating.teams etc.
We have an event in late September 2027 that requires seating in database view. This event only happens once every 2 years (and it our only event that requires the seating module). The current planned sunset date doesn't leave us time to try out a new option.
This functionality would be extremely helpful for teams that rely on NXT for event management. Right now, important participant details stored in Group/Seating Notes are only visible in Database View, which creates gaps, extra lookups, and inconsistent workflows when staff are working primarily in NXT.
Having Group/Seating Notes surfaced in NXT would significantly improve event operations, reduce reliance on workarounds, and support more accurate, accessible participant information across teams. This would be a meaningful improvement for users who need full visibility into event data without switching between views.
We also use this to track seating requests and to note how many tickets a sponsor intends to use (using all, using some, using none, usage unknown) so that staff know if and how to follow-up.
This is particularly important for users with fall events as the 9/15/2027 DBV sunset approaches.
Also see this related (but different) idea: https://renxt.ideas.aha.io/ideas/RENXT-I-7088
We have an event in late September 2027 that requires seating in database view. This event only happens once every 2 years (and it our only event that requires the seating module). The current planned sunset date doesn't leave us time to try out a new option.
This functionality would be extremely helpful for teams that rely on NXT for event management. Right now, important participant details stored in Group/Seating Notes are only visible in Database View, which creates gaps, extra lookups, and inconsistent workflows when staff are working primarily in NXT.
Having Group/Seating Notes surfaced in NXT would significantly improve event operations, reduce reliance on workarounds, and support more accurate, accessible participant information across teams. This would be a meaningful improvement for users who need full visibility into event data without switching between views.
We also use this to track seating requests and to note how many tickets a sponsor intends to use (using all, using some, using none, usage unknown) so that staff know if and how to follow-up.