Always send initOrganization and orgUserHasExistingUser in invite URL

[vikfox]

Fixes #7481.

The web vault bundled with 1.37.0 (2026.6.4) requires seven query parameters in the accept-organization URL:

fromUrlParams(e){ return null==e ? null :
  isGuid(e.organizationId) && isGuid(e.organizationUserId)
  && null!=e.email && null!=e.token && null!=e.organizationName
  && null!=e.initOrganization && null!=e.orgUserHasExistingUser
    ? new bi({...}) : null }

send_invite() never appended initOrganization, and appended orgUserHasExistingUser only when the invited user already had an account. With either missing, fromUrlParams returns null and the component shows inviteAcceptFailed without sending any request to the server — which is why the log shows no POST /api/organizations/<org_id>/users/<member_id>/accept at all.

This regressed in 1.37.0: web vault 2026.4.1 (shipped with 1.36.0) had the same logic under the name fromParams and required only the two GUIDs, reading the rest null-safely.

This patch always sends both parameters. Verified on 1.37.0 with SMTP enabled: before the change the invite link is rejected client-side; after appending &initOrganization=false manually the invite is accepted, the membership moves to Accepted, and confirmation by the owner works as usual. Reported independently by another user in the issue.

[Jonty16117]

im having the same issue as well, no user is able to sign up using invite link from email 😭

[albertogalisteo]

same issue

[davidSGE]

Need the fix asap. Was running into problems multiple times today in business context...

[RomanIzvozchikov]

The same problem

[Jonty16117]

same here, im unable to add members at this point, @dani-garcia could u please have a look at this pr?

tx in advance :D

[RouL]

Unfortunately we also got hit by this with several invites in the queue yesterday. But I don't wanna complain, you people do a great job here. :)

(A quick bugfix release would still be appreciated, before the other departments loose patience. ^^)

[BlackDex]

@stefan0xC does this indeed fixes that invite issue?

[sandervandegeijn]

We are running into the same problem, we are using SSO. How can we help, do we have a list of scenarios that need to be tested?

[stefan0xC]

@stefan0xC does this indeed fixes that invite issue?

It does. (I've tested it with both an existing and also a new user.)

[sandervandegeijn]

Did you use the SSO flow or the normal login flow? Do we need to test other flows?

[Exonip]

I can also confirm this fixes the invite issue via email when using SSO. This needs to be merged and releases asap

[Wiredista]

For those who use Docker, while the PR is pending, you can replace your container with the fixed fork easily.
In the docker-compose.yml change the line with image: vaultwarden/server:latest to build: https://github.com/vikfox/vaultwarden.git#fix/invite-init-organization

Docker compose file will look like this:

services:
  vaultwarden:
-   image: vaultwarden/server:latest 
+   build: https://github.com/vikfox/vaultwarden.git#fix/invite-init-organization
    container_name: vaultwarden
...

Then run docker compose up -d --build. It'll build the container image directly from the forked repository.

dont forget to change back later
update: you can also use the link for this repo, while the repository image doesn't get the update.

[BlackDex]

I Finally had some time to do some extra checking.
I checked the flows using SSO and SSO_ONLY, and also invites via the /admin portal.
This fix seems to keep those invites working too without any issues as far as i could detect.

Thanks @vikfox