Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delight: Highlight the importance of the security passphrase #22073

Open
daniellekirkwood opened this issue May 4, 2022 · 8 comments
Open

Delight: Highlight the importance of the security passphrase #22073

daniellekirkwood opened this issue May 4, 2022 · 8 comments
Labels
A-E2EE-Key-Backup O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience T-Enhancement X-Needs-Design X-Needs-Product More input needed from the Product team Z-NewUserJourney

Comments

@daniellekirkwood
Copy link
Contributor

daniellekirkwood commented May 4, 2022

During a user's first session we don't explain the security passphrase to users. If a user does not set it up correctly, or loses this it makes it much harder to log in (impacting D1 and user success!)

At some point during the first session we should take time to educate users and ensure that they're set up for success when they choose to return to Element.

@daniellekirkwood daniellekirkwood self-assigned this May 4, 2022
@duxovni duxovni added A-E2EE-Key-Backup O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience labels May 4, 2022
@aaronraimist
Copy link
Collaborator

aaronraimist commented May 6, 2022

@germain-gg
Copy link
Contributor

I'm not so sure this would impact D1 that much.
The risk with not setting up your security passphrase is that you loose the ability to retrieve your encrypted messages when you create a new session.
This would typically happen much later. And users could totally be deterred from using Matrix/Element ever again when they realise they've lost everything. But I wonder how often people will hit that issue in the first 24 hours of using the product

@daniellekirkwood
Copy link
Contributor Author

I'm not so sure this would impact D1 that much. The risk with not setting up your security passphrase is that you loose the ability to retrieve your encrypted messages when you create a new session. This would typically happen much later. And users could totally be deterred from using Matrix/Element ever again when they realise they've lost everything. But I wonder how often people will hit that issue in the first 24 hours of using the product

Thinking out loud; If D1 is "returned users in a 24h period" and users are using the Web product they may need to sign in again when they return tomorrow...

In my head it looks like this: User creates account, user validates email, user signs in, user starts DM and sends message, user closes browser tab, user opens element tomorrow, user needs to sign-in, user can't sign in because no security passphrase...

I guess we could find out how common it is to signin vs already be signed in when you return to app.element.io?

@t3chguy
Copy link
Member

t3chguy commented May 10, 2022

In my head it looks like this: User creates account, user validates email, user signs in, user starts DM and sends message, user closes browser tab, user opens element tomorrow, user needs to sign-in, user can't sign in because no security passphrase...

If you don't explicitly log out, closing the tab will not require you to sign-in again. Matrix sessions never expire unless manually done so by you on one of your other devices or your server admin. The exception to this is if you are running a browser like Tor which is amnesiac and forgets everything when you close it.

@daniellekirkwood
Copy link
Contributor Author

Good to know - I have adjusted the Occasion and Priority rating of this issue accordingly

@daniellekirkwood
Copy link
Contributor Author

Moving to "Next" as it's not prioritised just yet but we marked it as important

@daniellekirkwood daniellekirkwood added the X-Needs-Product More input needed from the Product team label May 19, 2022
@daniellekirkwood daniellekirkwood removed their assignment Jul 19, 2022
@daniellekirkwood
Copy link
Contributor Author

We should also make the language consistent

@daniellekirkwood
Copy link
Contributor Author

@pmaier1 & @americanrefugee

Also see this issue that was onboarding feedback...

Feel free to close this if it's a duplicate of things you're already tracking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE-Key-Backup O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience T-Enhancement X-Needs-Design X-Needs-Product More input needed from the Product team Z-NewUserJourney
Projects
None yet
Development

No branches or pull requests

5 participants