I also need the profile pages for each delegate. Ideally, these profile pages should be stored in an overarching database so that they can be used in multiple events. Our community is tight and many of our members attend many, if not all of our events. It is a PITA for them having to fill in the same information over and over again whenever we have a new event.
This is why we have created an over arching always on event community. Then we can sell tickets to specific events, streams etc. That way we only ever need a speaker or delegate to register once, and can access their entire purchase history etc in one single location. We will still have landing pages for events, and potentially outside ticketing for in person only attendance, but for replays and the like believe we will direct everyone to the single always on community hub.
I was wondering if this was possible. I am still fully immersed in our first event. It’s hybrid and it starts in 18 hours from now. So no time to experiment yet. Thank you very much. It’s great to know you have done this. One sheep over the dam…
In the process of doing it. Feel you- hybrid is always a little more stressful. Wishing you every success, hope in person and online goes flawlessly, happy to share notes when I have pinned down all the logistics.
Hey Andrew, the first version of this is actually already in the Event Lobby. You might just not have the direct messaging and delegate directory turned on. If you head over to the setup area and then go to the Event Lobby section, there should be a setting there to turn on direct messaging. Not everything that you've mentioned here exists in this first version, but it's a good bare-bones ability to browse attendees, create private messages, etc.
Got it. Understood and that is handy functionality. I am exploring a workaround now, as having full rich content pages for each delegate is the ideal scenario in my use case (as its always on event community) but understand it will not be a big need for most users.
Hi Andrew - just a heads up that this was largely delivered a while back (looks like we had a duplicate feature request). So i’m marking this as complete.