I've been working on this idea for a while, and most of you have described the same trap. You need a volunteer to run one or several events, and the only way to let them is to hand over your whole contact database and your finances. But there are different events and different needs. So I'd like to test the shape with you before we build it.
The idea is to maintain the current role of Event Manager, which currently grants access to all events. However, you can also limit this access and assign the person to specific events by choosing from one of three levels of access:
Check-in assistant - welcome people at the door, handle walk-ins. Sees their assigned events and who's registered. Checks people in, signs up whoever turns up, takes payment at the door. Cannot edit the event or its registrations.
Registration manager - help with accepting and managing registrations, including waitlist, before/during/post event. Has access above, plus edit and cancel registrations, run the waitlist, export their own list, and email their own registrants.
Event lead - complete event management, including tickets, emails and event details, for assigned events. Can duplicate an event they run.
Imptortant note: At every level there is no access to full contact list and details (only registration information), member records, invoices or payments, no refunds, and no sight of any event they haven't been assigned to.
I'd like your reaction to some of that:
Do these three levels match how your events are actually staffed, or is something sitting in the wrong one? Maybe overkill even.
Assignment is per event. If you run 100 or more events a year, does that work? We will copy the assignment with event.
A person gets one level across all their events, you will assign the new role same way as you do now. Does that break anyone who wears two hats — a committee chair at one event, a door volunteer at another?
Any other concerns?
On the admin mobile app, you'll probably notice the quickest benefits. It already performs the essential functions of a check-in assistant — QR and manual check-in, managing registrations, guests, waitlists, and recording payments. Currently, door volunteers can't use it because it needs full event manager access. Once access can be limited, the app will be accessible to those requesting it for their assigned events.
Please let me know your thoughts.
Best,
Katya Tyukina,
Sr. Director of Product, Momentive software.
Hello everyone,
I've been working on this idea for a while, and most of you have described the same trap. You need a volunteer to run one or several events, and the only way to let them is to hand over your whole contact database and your finances. But there are different events and different needs. So I'd like to test the shape with you before we build it.
The idea is to maintain the current role of Event Manager, which currently grants access to all events. However, you can also limit this access and assign the person to specific events by choosing from one of three levels of access:
Check-in assistant - welcome people at the door, handle walk-ins. Sees their assigned events and who's registered. Checks people in, signs up whoever turns up, takes payment at the door. Cannot edit the event or its registrations.
I agree. We have this kind of a need where a person is assigned an event (trip leader for a ski trip). I would love/need to have the ability to assign a person as the trip leader and have them see all the information on each person who has signed up for their trip only. They should not be able to see other trip leader's travelers or financials. And they should not be allowed to change the content of the web pages in any way. They should be allowed to record payments and any other additional information needed. To complicate this process further, I would also like/need to be able to assign a level to the treasurer where they can see all trips and travelers on those trips and all of the financial information but not be able to modify web pages. I know this could be a hard thing to code but I think a well thought out layered system of access levels could be the answer.
allenknox
I agree. We have this kind of a need where a person is assigned an event (trip leader for a ski trip). I would love/need to have the ability to assign a person as the trip leader and have them see all the information on each person who has signed up for their trip only. They should not be able to see other trip leader's travelers or financials. And they should not be allowed to change the content of the web pages in any way. They should be allowed to record payments and any other additional information needed. To complicate this process further, I would also like/need to be able to assign a level to the treasurer where they can see all trips and travelers on those trips and all of the financial information but not be able to modify web pages. I know this could be a hard thing to code but I think a well thought out layered system of access levels could be the answer.