Invalid email token journey (account already created) not designed

[bentateart]

Once you've clicked on the invite email and created an account, if you then click on the same link again the user sees an error message about an invalid token. If the user is already logged in they are directed to the 'Registers' landing page showing the error messages, if they are not logged in they are directed to the login form showing the error messages. The error messages suggest that the user is unable to do something, but the journeys can continue.

URL:

https://managing-registers-staging.cloudapps.digital/

Steps to recreate:

1. Create account
2. Go back to inbox
3. Click on the invite link again

Expected result:

Not sure.

Actual result:

[elliecraven]

if I'm understanding correctly:
for this release - users with an invalid token should not be able to create an account or access anything behind auth, perhaps should be directed to 'request a new token' (i.e. get invited again)? @bentateart

for next iteration - better way of handling token expiry as part of account creation/management journeys

[bentateart]

@elliecraven
Not quite.
I haven't tested with an expired token (there's no design for an expired token journey).
This is journey's where the user has already created an account and then clicks the same invite token link again. The user sees error messages about invalid tokens, but they can still log in fine.

[elliecraven]

ah I see @bentateart so perhaps in this iteration:
change error message to 'that invite token has expired - return to login page' would work? what do you think @danmitchell- ?

Assumption: users are clicking the link in the old invite email to find the login page