[$120] P3: Update Invited Registered User Workflow

[ajefts]

Objective: Update email templates sent to registered platform users when they are invited to a project to include 'Join Project' or 'Decline' buttons, which when clicked automatically manage their acceptance or decline of invitation in the platform. This will improve the efficiency of the workflow that exists today, wherein: An invited registered user receives an invitation email, they click the invitation link in the email, they are brought into Connect and see a pop-up for Join/Decline, and have to click on their choice in the platform.

Requirements - Workflow:

[Imagining that users has already completed the steps of sending invitation/receiving invitation]

• Registered user receives project invitation email

• Registered user sees button options of 'Join Project' or 'Decline' in the email body

  • Option A: Registered user clicks 'Join Project.' User should be automatically joined to the project.

  • Option B: Registered user clicks 'Decline.' User should not be joined to the project and should not see the project listed on their 'all projects' dashboard on next login.

[ajefts]

Link to feature: https://tcprod.productboard.com/feature-board/planning/features/2761674

[maxceem]

It looks like there are two parts in this issue to be done:

1. In the Connect App create links which users can follow to automatically accept and decline invitation. I'm thinking about creating the next links:

   // link to automatically accept invitation
   http://local.topcoder-dev.com:3000/projects/8369?invitation=accept
   
   // link to automatically decline invitation
   http://local.topcoder-dev.com:3000/projects/8369?invitation=decline
   

   So if user follows such a link we should show the loading indicator during we are sending request to the server to accept/decline the invitation.

   • If invitation is accepted we start loading the project (continue showing loader). We should remove ?invitation=accept from the URL as soon as invitation is accepted. It's better to do by replacing the current URL so there is not URL with ?invitation=accept in browser history.
   • if invitation is declined we can redirect to the project listing page.
   • if user is already a member of the project no matter which link we use, we just show the project. Same like in the first case we should remove ?invitation=... from the URL.
   • if user is not a member, but there is an error during invitation accept or decline we should show the error page (with error from the server)

   @RishiRajSahu @vikasrohit what do you think about security risks with such links?

2. After we implement the first part, we can update email template by adding these two links and button to accept and decline invitations.

[RishiRajSahu]

@maxceem I don't think there should be any security risk by creating such URLs to accept/decline the invitation, because as per my understanding we update the PENDING invites present for that user for a particular project, so even if those params are changed manually and there is no PENDING invite present for that project/member combination then there will be an error.

[maxceem]

Right, we only updating a PENDING invitation, otherwise there would be an error.

[maxceem]

Sum up:
Implement the first part of this task, described in #3311 (comment)

For testing the next project can be used http://local.topcoder-dev.com:3000/projects/8370 or create a new project. See demo video on how I use user pshah_manger to invite user pshah_customer.