-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Disable registration of new users
By default, anyone who can access your instance can register for a new account. To disable this, set the SIGNUPS_ALLOWED
env variable to false
:
docker run -d --name bitwarden \
-e SIGNUPS_ALLOWED=false \
-v /vw-data/:/data/ \
-p 80:80 \
vaultwarden/server:latest
Note that when SIGNUPS_ALLOWED=false
, the Create Account
button will still be shown in the web vault UI, but actually attempting to create an account will result in an error message. Upstream Bitwarden isn't designed to allow disabling signups, so this can't be worked around easily.
Even when SIGNUPS_ALLOWED=false
, an existing user who is an organization owner or admin can still invite new users. If you want to disable this as well, see Disable invitations.
You can restrict registration to email addresses from certain domains by setting SIGNUPS_DOMAINS_WHITELIST
accordingly. For example:
-
SIGNUPS_DOMAINS_WHITELIST=example.com
(single domain) -
SIGNUPS_DOMAINS_WHITELIST=example.com,example.net,example.org
(multiple domains)
Warning
If SIGNUPS_DOMAINS_WHITELIST
is set, then the value of SIGNUPS_ALLOWED
is ignored.
You may also want to set SIGNUPS_VERIFY=true
, which would require email verification before a newly-registered user can successfully log in. This would prevent someone from registering with a fake email address that has the proper domain.
The vaultwarden admin can invite anyone via the admin page, regardless of any of the restrictions above.
- Which container image to use
- Starting a container
- Updating the vaultwarden image
- Using Docker Compose
- Using Podman
- Building your own docker image
- Building binary
- Pre-built binaries
- Third-party packages
- Deployment examples
- Proxy examples
- Logrotate example
- Overview
- Disable registration of new users
- Disable invitations
- Enabling admin page
- Disable the admin token
- Enabling WebSocket notifications
- Enabling Mobile Client push notification
- Enabling U2F and FIDO2 WebAuthn authentication
- Enabling YubiKey OTP authentication
- Changing persistent data location
- Changing the API request size limit
- Changing the number of workers
- SMTP configuration
- Translating the email templates
- Password hint display
- Disabling or overriding the Vault interface hosting
- Logging
- Creating a systemd service
- Syncing users from LDAP
- Using an alternate base dir (subdir/subpath)
- Other configuration