[GH-ISSUE #186] Disabling signups and invitations does not remove "Create Account" box on login #92

New issue

Closed

opened 2026-03-03 01:24:48 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 01:24:48 +03:00

Owner

Originally created by @flamechair on GitHub (Sep 16, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/186

Hi,

I've disabled login via SIGNUPS_ALLOWED=false and INVITATIONS_ALLOWED=false, yet when I go to the web ui it still shows the option to create an account:

I've verified that you cannot actually create an account, but it might be better UX to disable the "Create Account" box when account creation is disabled, instead of letting them find out after they fill out the whole form.

Originally created by @flamechair on GitHub (Sep 16, 2018). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/186 Hi, I've disabled login via `SIGNUPS_ALLOWED=false` and `INVITATIONS_ALLOWED=false`, yet when I go to the web ui it still shows the option to create an account: ![image](https://user-images.githubusercontent.com/8901422/45601652-3483e880-b9d6-11e8-8587-756145036107.png) I've verified that you cannot actually create an account, but it might be better UX to disable the "Create Account" box when account creation is disabled, instead of letting them find out after they fill out the whole form.

kerem closed this issue

2026-03-03 01:24:49 +03:00

kerem commented

2026-03-03 01:24:49 +03:00

Author

Owner

@mprasil commented on GitHub (Sep 16, 2018):

Unfortunately this is upstream thing. We just pack Bitwarden Vault "as is". (Some other differences are described in the Readme) I'm going to close this as there isn't much we can do here as far as I know, but if you think there's something the API can do to let the Vault know to disable or hide the button, feel free to reopen.

BTW even with registrations disabled, the users can be invited to register, so unless you also disabled that, there is a chance that the button might be needed in some cases.

@mprasil commented on GitHub (Sep 16, 2018): Unfortunately this is upstream thing. We just pack Bitwarden Vault "as is". (Some other differences are described in the Readme) I'm going to close this as there isn't much we can do here as far as I know, but if you think there's something the API can do to let the Vault know to disable or hide the button, feel free to reopen. BTW even with registrations disabled, the users can be invited to register, so unless you also disabled that, there is a chance that the button might be needed in some cases.

kerem referenced this issue

2026-03-03 02:19:59 +03:00

[PR #92] [MERGED] Return 404 in case the path doesn't match instead of 500 #2606