# Export event data is a bit painful, and email addresses would be useful **URL:** \ **Category:** UX\ **Tags:** events\ **Created:** [October 18, 2022, 1:06am UTC](https://meta.discourse.org/t/export-event-data-is-a-bit-painful-and-email-addresses-would-be-useful/242153 "2022-10-18T01:06:49Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Ethsim2](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ethsim2/32/522255_2.png) [@Ethsim2](https://meta.discourse.org/u/Ethsim2)\ **Post date:** [July 31, 2025, 6:42am UTC](https://meta.discourse.org/t/export-event-data-is-a-bit-painful-and-email-addresses-would-be-useful/242153/3 "2025-07-31T06:42:40Z")
+1 — we strongly support this. We use Discourse’s `[event]` syntax (via the Calendar plugin) to schedule and coordinate official council meetings — each event lives inside a dedicated topic, and we encourage members to RSVP using the built-in interface. The problem is: we currently have no clean way to extract that RSVP data in a usable format. For public engagement sessions, executive meetings, and internal briefings, it would be incredibly useful to export: - Event topic title + URL - Display name / username of RSVPs - RSVP status (going / interested / not going) - Email address (admin-only, for attendance logs or direct follow-up) - Timestamp of RSVP (if possible) Our clerks and chairs often don’t use Discourse themselves, so being able to download a CSV and share attendance with them is essential. Understandably, email visibility would need to be permission-limited to site staff or group moderators — but without it, the export loses most of its administrative value. This kind of structured export would significantly improve the plugin’s usefulness for real-world orgs that use Discourse to coordinate offline meetings. Happy to provide a sample `.csv` layout if helpful! --- _[View the full topic](https://meta.discourse.org/t/export-event-data-is-a-bit-painful-and-email-addresses-would-be-useful/242153)._