When invitations_allowed is set to false, the button "Resend invitation" in the organization view does not work. Instead, the error message "Invitations are not allowed" is shown.
Your environment (Generated via diagnostics page)
Vaultwarden version: v1.30.5
Web-vault version: v2024.1.2b
OS/Arch: linux/x86_64
Running within a container: true (Base: Debian)
Environment settings overridden: false
Uses a reverse proxy: true
IP Header check: true (X-Forwarded-For)
Internet access: true
Internet access via a proxy: false
DNS Check: true
Browser/Server Time Check: true
Server/NTP Time Check: true
Domain Configuration Check: true
HTTPS Check: true
Database type: SQLite
Database version: 3.44.0
Clients used:
Reverse proxy and version:
Other relevant information:
Steps to reproduce
Disable invitations_allowed
Invite an existing user to an organization
On the members tab, click the three-dot-menu next to the user and select "resend invitation"
Expected behaviour
The invitation email is resent.
Actual behaviour
The error message "Invitations are not allowed" is shown.
Originally created by @tribut on GitHub (Jun 12, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4640
### Subject of the issue
When `invitations_allowed` is set to `false`, the button "Resend invitation" in the organization view does not work. Instead, the error message "Invitations are not allowed" is shown.
### Your environment (Generated via diagnostics page)
* Vaultwarden version: v1.30.5
* Web-vault version: v2024.1.2b
* OS/Arch: linux/x86_64
* Running within a container: true (Base: Debian)
* Environment settings overridden: false
* Uses a reverse proxy: true
* IP Header check: true (X-Forwarded-For)
* Internet access: true
* Internet access via a proxy: false
* DNS Check: true
* Browser/Server Time Check: true
* Server/NTP Time Check: true
* Domain Configuration Check: true
* HTTPS Check: true
* Database type: SQLite
* Database version: 3.44.0
* Clients used:
* Reverse proxy and version:
* Other relevant information:
### Steps to reproduce
1. Disable `invitations_allowed`
2. Invite an existing user to an organization
3. On the members tab, click the three-dot-menu next to the user and select "resend invitation"
### Expected behaviour
The invitation email is resent.
### Actual behaviour
The error message "Invitations are not allowed" is shown.
GiteaMirror
added the bug label 2026-04-23 06:28:46 -05:00
Thanks, looks like we need to move that check and depend on if the user already had an account on the system.
<!-- gh-comment-id:2163043056 -->
@BlackDex commented on GitHub (Jun 12, 2024):
Thanks, looks like we need to move that check and depend on if the user already had an account on the system.
<!-- gh-comment-id:2188085873 -->
@stefan0xC commented on GitHub (Jun 25, 2024):
This check is also wrong, if a user already exists they should be accepted immediately if mail is disabled:
https://github.com/dani-garcia/vaultwarden/blob/a4c7fadbf4ffa242fb78ebd152080028e7f2993c/src/api/core/organizations.rs#L1004-L1006
(This should only happen in case you had mail enabled invited a user and then disabled mails before the user accepted the invitation.)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @tribut on GitHub (Jun 12, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4640
Subject of the issue
When
invitations_allowedis set tofalse, the button "Resend invitation" in the organization view does not work. Instead, the error message "Invitations are not allowed" is shown.Your environment (Generated via diagnostics page)
Steps to reproduce
invitations_allowedExpected behaviour
The invitation email is resent.
Actual behaviour
The error message "Invitations are not allowed" is shown.
@BlackDex commented on GitHub (Jun 12, 2024):
Thanks, looks like we need to move that check and depend on if the user already had an account on the system.
@stefan0xC commented on GitHub (Jun 25, 2024):
This check is also wrong, if a user already exists they should be accepted immediately if mail is disabled:
https://github.com/dani-garcia/vaultwarden/blob/a4c7fadbf4ffa242fb78ebd152080028e7f2993c/src/api/core/organizations.rs#L1004-L1006
(This should only happen in case you had mail enabled invited a user and then disabled mails before the user accepted the invitation.)