Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Authenticate users email for sending studies #91

Open
will-molloy opened this issue Mar 13, 2018 · 3 comments
Open

Authenticate users email for sending studies #91

will-molloy opened this issue Mar 13, 2018 · 3 comments
Labels

Comments

@will-molloy
Copy link
Contributor

will-molloy commented Mar 13, 2018

Currently, studies are sent to participants from a dummy gmail account
(see org.project36.qualopt.service.StudyService). AFAIK they should be sent from the user who created the study.

@softeng-701 I think this is similar to #37/#44 so medium sized issue.

@kblincoe kblincoe added the large label Mar 15, 2018
@kblincoe
Copy link
Owner

This one will require some investigation. To send the email from the user who created the study, you would need their email server, username, password, etc. Which users might not be willing to share.

@kblincoe
Copy link
Owner

Per the fix in #114, it might be better to leave as one sender (but somehow have responses also sent to the person who owns the study?)

@will-molloy
Copy link
Contributor Author

will-molloy commented Mar 19, 2018

Ok, this issue could be then: Study invitations are being sent from a single, QualOpt email account but the participants have no indication which QualOpt user sent to them. When participants reply to these study invitations it should be forwarded to the user who created the study.

But I think the design can be better. Why delegate the QualOpt account for replying to study creators? Instead invitations could include a link to the study page which could have the users email so participants can contact them directly and this can come under #42.

I guess I'm just not sure how the emailing was suppose to work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants