Event Organizer able to access Registration data for their event data
Limited or read-only access by Organizer to registration data for their event.
Currently our Events Manager has to produce a spread sheet every day and email it to the respective Reservationist (Organizer), doing this for EVERY event. An impossible task. And if we need to circulate spreadsheets, why do we need WA? (Sorry)
Bruce Doll commented
There is a small box for "will bring to share" for an event, but it can only be seen by administrators. It needs to be visible to all members to facilitate coordination. Thanks!
We too need the option for assigning a level for short term event chairs to be able to export event lists and view event info without having the full admin privileges of editing member profiles, recording payments and viewing everything in the system. Each year that person (needing event export ability) may change to a different person. We found that we can't even assign them as "view only" admin because that allows viewing of all data and cannot send group emails ( a necessary function when you are in charge of an event).
We have a similar problem where we want our co-chairs to have access to only the registration list. Currently, the event manager setting allows the user to do too much, such as emailing members, editing invoices, etc. What we really need a lower user level that can only view the event registrations or maybe just edit the events, but not anything else.
This would be a convenient feature for us. we have separate field trip leaders who would like to have the registration information prior to the trip (to arrange carpools) as well as the day of the trip to check in participants. If an admin is not there, they can't verify registrations.
Read it finally, sorry for the delay. Thank you so much for the details, Randall. You definitely have a complicated setup. My key understanding is that you have special people who you do not want to give normal Admin access (so they can do what they need to do), you need to restrict their access a lot.
Randall Rensch commented
PS: Thank you for your interest, in asking for details.
Randall Rensch commented
We are a ski club, and run events of various types. Some are evening get-togethers involving no charge by us (eg. a happy hour, dinner or ice skating at a local venue) some involve a charge (e.g. a party or group-tickets film), some are weekend stays at our lodge in New England. Of those stays, some are bus trips requiring payment in advance, others are carpools where people pay at the end of the weekend.
Each event has a "reservationist" who takes reservations, keeps track of "sales," arranged drivers and riders, assigns rooms or whatever the event entails. For decades we've done this using spreadsheets and/or our own proprietary software (a PHP-written CMS backend that produced our website calendar, created emails, managed data, stored documents securely (.htaccess level) and stored how-to screens). Understandably, we didn't want to be dependent on one or two members who created that system, which is why we turned to WA, which had meanwhile grown more robust and versatile.
Unfortunately, not quite versatile enough for us to use without requiring way more training and managerial effort than should be necessary. Previously, an event would be put on the calendar and various people would make it happen. But now, especially now that this year we decided to try requiring Registration for almost all events of all types, our Reservationists can't even reliably get the registrant data! They get an email, but what if it goes missing? And having gotten all the registrant emails, then they have to, what, create a spreadsheet or some such document? That's missing the point of this system, eh?
So now someone on our management committee (i.e., and Admin) has to export the data, ideally every day, to each and every Reservationist! Multiply that, during our peak season, to two or three local events every couple of weeks, and four weekends a month, and it just gets silly to even consider.
It would work so much better if each reservationist could access the Registrant data for their respective event, ideally with the ability to add or revise data and add or remove registrations, without giving them access to the whole system (with the obvious data and privacy risks in that). When the particular event is over, we would then want to cancel that Reservationists' access either manually or automatically.
By the way, we've always called them Reservationists, but that's also an important distinction. The person who organizes and event is not necessarily the person tracking reservations. Sometimes yes, sometimes no. And sometimes there is more than one organizer. Yet we're limited to one Organizer per event, with our automatic emails going out with their personal address as reply-to. That's both a privacy and a security issue (about which I've placed another wish on the wishlist already), so for each event we create an autoforward at our domain registrar, which is the one we publish and (after putting into our Contacts list and setting preferences so it won't get all our emails), is the one we specify as Organizer.
I hope that gives you a sense of our workflow. I'm not sure my offhand description is as organized as our procedures themselves are, but they've worked for decades, and now with WA, some of our people have gotten pretty confused. Some of it is just the transition from paper to computer, but some is a result of having to shoehorn our systems into your capabilities, which are great in some ways, but in others very limited or inflexible. (For example, the Registration form itself, which I've also already mentioned on the Wishlist).
I'd be happy to walk you through some actual events if that would help. But the bottom line is: help us distribute the workload so that our individuals who volunteer their time to help with an event can truly collaborate and each do a part of the job, without requiring more than supervisory involvement by our management committee members and webmaster, who are also volunteers.
Could you describe how you organize your events? What are the roles you have? Who you communication with each other? What is the workflow, who does what and who has or has not access to some data? This would greatly help us to understand the problem.