VEuPathDB / service-dataset-access

Apache License 2.0
0 stars 2 forks source link

Study Access Dashboard: Emails to be added to dashboard automatically when ClinEpi account is made #99

Open nkittur-uga opened 2 years ago

nkittur-uga commented 2 years ago

When we add a provider email address to a data access dashboard and that email address does not belong to an existing ClinEpiDB account, an email is automatically generated to ask that person to make an account. Current behavior is that the outreach team has to go back and manually add that email address to the data access dashboard after we confirm that they have indeed made an account.

A useful feature would be that when a user gets the email and makes a ClinEpiDB account, then their email address should be automatically added to the study dashboard.

dmfalke commented 8 months ago

Having just read this issue again, I'm not sure this is a front-end issue.

danicahelb commented 5 months ago

April 12, 2024 - i confirmed that the new account is not automatically given study team member access once the account is created. ClinEpiDB staff need to be notified when the account is made and manually add the new account to the list of study team members. this is not urgent to fix at this moment

The process looks like this:

  1. go to the Management Dashboard of any study and click on the + Add Team Members button
  2. add an email address that is NOT currently associated with a VEuPathDB account
  3. the new team member gets an email that looks like this, and copies/pastes the link in their browserimage
  4. the link take the new team member to the account creation page, where they register the email address to a VEuPathDB account
  5. the new team member must email help@clinepidb.org to let us know that the account has been created
  6. clinepi staff will go to the Management Dashboard of any study and click on the + Add Team Members button and add the new team member email address
dmfalke commented 5 months ago

@dmgaldi tagging you, in case you weren't aware of this request. The issue was in the wrong repo... sorry about that.