Details
-
Type:
Sub-task
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 5.8.0-b1
-
Component/s: None
-
Labels:None
Description
The link from the email in CORE-4844 should lead to an acceptance page if authenticated, or a login page otherwise.
Following the link should probably set a cookie or session variable that links to the account_management_invitations record.
The authentication page should have 2 buttons: Accept and Reject.
Accept should convert a account_management_invitations record to the equivalent contact_permissions records with the authenticated user's primary contact as the contact_id. This should not work if the primary contact's email doesn't match that of the account_management_invitations record.
Reject should delete a account_management_invitations record.
Appropriate messages should be displayed.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description | TBD |
The link from the email in Following the link should probably set a cookie or session variable that links to the client_access_invitations record. The authentication page should have 2 buttons: Accept and Reject. Accept should convert a client_access_invitations record to the equivalent contact_permissions records with the authenticated user's primary contact as the contact_id. This should not work if the primary contact's email doesn't match that of the client_access_invitations record. Reject should delete a client_access_invitations record. Appropriate messages should be displayed. |
| Summary | Shared Access - Invitation Acceptance | Managed Accounts - Invitation Acceptance |
| Description |
The link from the email in Following the link should probably set a cookie or session variable that links to the client_access_invitations record. The authentication page should have 2 buttons: Accept and Reject. Accept should convert a client_access_invitations record to the equivalent contact_permissions records with the authenticated user's primary contact as the contact_id. This should not work if the primary contact's email doesn't match that of the client_access_invitations record. Reject should delete a client_access_invitations record. Appropriate messages should be displayed. |
The link from the email in Following the link should probably set a cookie or session variable that links to the account_management_invitations record. The authentication page should have 2 buttons: Accept and Reject. Accept should convert a account_management_invitations record to the equivalent contact_permissions records with the authenticated user's primary contact as the contact_id. This should not work if the primary contact's email doesn't match that of the client_access_invitations record. Reject should delete a account_management_invitations record. Appropriate messages should be displayed. |
| Description |
The link from the email in Following the link should probably set a cookie or session variable that links to the account_management_invitations record. The authentication page should have 2 buttons: Accept and Reject. Accept should convert a account_management_invitations record to the equivalent contact_permissions records with the authenticated user's primary contact as the contact_id. This should not work if the primary contact's email doesn't match that of the client_access_invitations record. Reject should delete a account_management_invitations record. Appropriate messages should be displayed. |
The link from the email in Following the link should probably set a cookie or session variable that links to the account_management_invitations record. The authentication page should have 2 buttons: Accept and Reject. Accept should convert a account_management_invitations record to the equivalent contact_permissions records with the authenticated user's primary contact as the contact_id. This should not work if the primary contact's email doesn't match that of the account_management_invitations record. Reject should delete a account_management_invitations record. Appropriate messages should be displayed. |
| Assignee | Abdy Franco [ abdy ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 7 hours, 47 minutes [ 28020 ] | |
| Worklog Id | 16377 [ 16377 ] |
| Time Spent | 7 hours, 47 minutes [ 28020 ] | 1 day, 7 hours, 46 minutes [ 56760 ] |
| Worklog Id | 16381 [ 16381 ] |
| Time Spent | 1 day, 7 hours, 46 minutes [ 56760 ] | 2 days, 7 hours, 26 minutes [ 84360 ] |
| Worklog Id | 16383 [ 16383 ] |
| Status | In Progress [ 3 ] | In Review [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Status | In Review [ 5 ] | Closed [ 6 ] |
