The current 'Add a Mentor' flow is: * event organizer adds an email address of a mentor (who may or may not be registered with Webmaker) * mentor receives email to confirm their participation * once they have confirmed, the mentor's username / profile link show up on the event detail page HOWEVER If the event organizer adds a mentor by an email address but that user is registered with Webmaker under another email address, we should - if possible - allow them to choose which email/account they want to use to show up as a mentor on the Events Detail page. This may or may not be covered by login flows that allow a user to choose which email they want to sign in with... Flagging Matthew for thoughts. This is stemming from conversation with Kate on bug 1020356
For existing users, adding multiple email addresses could be a good feature of their profile page. That said, event invites probably shouldn't add new addresses to anyone's account, new or existing users. Better to assume that the address a person chose for Webmaker is the one they want to use. I think that the email used by the event organizer should only be used to deliver the invite. The Webmaker's account details should take over once someone confirms participation. I see it like this: * organizer adds mentor to event (email + auto temp ID) * webmaker sends an invite with a link that points to the temp ID * mentor clicks the link * mentors logs-in or signs-up * temp ID is replaced with mentor's ID and all their profile info * mentor says to organizer over coffee: "btw, i stopped using that earthlink.net email address weeks ago!" I might be missing something on how all this works. If I'm way off, let's discuss...
Whiteboard: events2, future → events2, future, [events-mentor]
Whiteboard: events2, future, [events-mentor] → [events2][june27][events-mentor]
Whiteboard: [events2][june27][events-mentor] → [events2] [events] [june27][events-mentor]
This is resolved by bug 1010426
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.