You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently no easy way to email people who have organized in the past. I have to be an organizers for that particular event to be able to see other organizer emails.
Every month when we try and find organizers we use a list we have complied by pulling individual organizer information from respective events.
Being able to email a list of past organizers without having to go search for each individual emails and compile our own list - would be hugely helpful. Whether this be sending an email via Bridge Troll or downloading a csv with organizer email addresses - any way of accessing that information would be helpful.
The text was updated successfully, but these errors were encountered:
lilliealbert
changed the title
A way to email organizers for a specific chapter
Add a way to email organizers for a specific chapter
Jan 11, 2016
lilliealbert
changed the title
Add a way to email organizers for a specific chapter
Add a way to email all past organizers from a specific chapter
Jan 11, 2016
Especially now that Bridgetroll has been modified to keep emails hidden from organizers. Now very tricky to contact former organizers, volunteers, and students.
There is currently no easy way to email people who have organized in the past. I have to be an organizers for that particular event to be able to see other organizer emails.
Every month when we try and find organizers we use a list we have complied by pulling individual organizer information from respective events.
Being able to email a list of past organizers without having to go search for each individual emails and compile our own list - would be hugely helpful. Whether this be sending an email via Bridge Troll or downloading a csv with organizer email addresses - any way of accessing that information would be helpful.
The text was updated successfully, but these errors were encountered: