Versions Compared

Old Version 8

changes.mady.by.user Hao Hu (Unlicensed)

Saved on

compared with

New Version 9

changes.mady.by.user Hao Hu (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Bob and Claire don't join the team
GoalAlice wants to invite Bob and Claire to join her Synapse team.
Primary actorAlice.
Secondary actorsBob and Claire.
PreconditionAlice has created a team and she is at her team's page.
Success endBob and Claire join the team.Failure endjoins the team, or Alice cancels the invitation to Bob.

Main success scenario

  1. Alice invites Bob and Claire to join her team by entering their his email addresses address and an optional invitation message.
  2. System sends Bob and Claire an email containing an invitation link to join Alice's team.
  3. Bob and Claire click clicks on the invitation link and reach a .
  4. Bob reaches a registration/sign in page .Bob and Claire click on "Sign up" and create their new Synapse accountsand creates his new Synapse account.
  5. System adds Bob and Claire's accounts account to Alice's team.
Error scenarios

1. One or more of the The email addresses entered donby Alice doesn't exist.

    1. System sends an email to Alice to notify her of the problem.
    2. Alice tries again with a different email address.
Alternative scenarios

1. Bob 2. System detects that the email address entered already has a Synapse account associated with the email address entered by Aliceit, presumably it's Bob's account.

    1. System sends Bob a membership invitation to Alice's team.
    2. Bob accepts the invitation and joins Alice's team.

4. Claire 3. Alice decides not to collaborate with Bob anymore and wants to cancel her invitation.

    1. Alice navigates to her team's page and clicks on the remove button associated with the pending invitation to Bob.
    2. System invalidates the invitation link sent to Bob.
      1. The link Bob received is no longer valid and directs to an error page.

4a. Bob already has a Synapse account associated with a different email address and is already signed in in his browser.

    1. System adds Bob's account to Alice's team.

4b. Bob already has a Synapse account associated with a different email address but isn't signed in.

    1. Claire Bob clicks on "Sign in" and logs signs in with her his existing account.
    2. System adds ClaireBob's account to Alice's team.

5. Bob clicked on the invitation link a long time* after it was issued. (* definition of long time to be specified)

    1. System sends a membership request to Alice's team instead of directly adding Bob to Alice's team.

...

Relevant questions

At step 4 in the main success scenario, should we skip the email validation process that precedes registering an account?
+ Easier to use for the user.
- Forces the user to register Synapse account with the email address the invitation was sent to.
Leaning towards yes, we should skip it.

Related to the above, should the invitation email have one link to a sign in/registration page; or two links, one to a sign in page and one to a registration page.
Tentatively a single link is preferred.

Should we allow batch inviting? Currently only one user can be invited at a time.
Not necessary.

Should we display pending invitations in Alice's team page and allow her to cancel them? This would remove the need for the alternative scenario on step 5.
Yes, it's a good idea as it enables alternative scenario step 3.

What happens if the invitee is already logged signed in to Synapse when they click the invitation link(s)?
Addressed by alternative scenario step 4a.

Should we allow existing users to be searched by their email address?
No, we shouldn't allow reverse searches because user email addresses aren't public.

Mockups

In progress

API

In progress