Scott B.

I’d go with 1️⃣ require the field to be in the public list.

🎟️ and Register

Wonderful 🙂

My bad, I was looking at the wrong event 🤦‍♂️

I just published a new event and not seeing the new button placement. The event was from a prior draft I had saved.

That would be a lot better 🙂

Might be a bit problematic if the registration takes place on another place (like our events do with reg via Hubspot). They actually won't be added until they actually register via that form.

Good updates and fixes. Can you share an example of the ephemeral message? One thought, the CTA to join the community might be better in another colour vs. with a white background.

Cleared cache and issue still exists in both Slack desktop app and mobile app. Don’t see the same issue on browsers. My user ID? Not sure how to get that in Slack. Timestamp: 4:01pm PT

Stephen C. We have a profile field today which uses selectable options. In this case Yes or No. Example attached. I was thinking we might be able to use that field type, user selected, to drive the preference for the user. Overall, anything user related, I'd prefer to be in the hands of users, not us, especially when that information is PII.