Invites account creation screen shows password as "optional"

( cbd7898d1d )

Priority/Severity: 2

desktop: latest versions of Firefox, Opera, Edge, Chrome
mobile: latest versions of Firefox, DuckDuckGo Browser, Chrome


Invites account creation screen shows password as “optional”

Passwort *
Mindestens 10 Zeichen (optional)

Passwort *
Mindestens 10 Zeichen

The bug is just cosmetic. It doesn’t change anything at the account creation process. Passwords are of course necessary for account creation, and account creation is possible. But it is confusing for users to see the password as “optional”.

The bug only accurs when creating an account over invitation links.

Reproducible steps:

  • create invitation
  • open invitation link
  • erroneous “password: optional” shows everytime on all platforms / browsers, with every invitation link


complete account creation screen via invitation link

complete standard account creation screen (without bug)

Thanks for your help!

The red star next to the word password shows that the field is required. It’s the hint text that says it’s optional.

Might need to check the translation string

I see its the same for the English language


and I found it on the locales




i dont think the code is 100% correct here.

Setting a password when initially accepting an invite is optional. If an invite is accepted without filling in the password field, the user will need to set a password after they log out and log back into the site.

I think that for almost all cases, setting a password when accepting an invite is more straightforward than setting the password at a later time. For that reason, I’m not sure that the password field should actually be optional. Possibly this is something that could be controlled by a site setting.

The current UI is confusing. The field is optional, but the star next to the password field name is used to mark required fields. If the field is to remain optional, the star should probably be removed from the password field on the accept-invite page.


I see, thanks for the clarification!