Linux CLI: organization not found

I’m trying to run the inheritparentpermissions.sh bash script from the Bitwarden CLI in Debian. The script always fails with “Organization not found.”.

What I did:

  • modified the script as stated and created supersecretstring and entered our organization-id as shown in the organization admin console
  • ran “bw login” and was successfully logged in
  • ran “inheritparentpermissions.sh”

This is the output from the console:

Thanks for any hints on what I’m doing wrong! :upside_down_face:

Where does the admin console show the organization id?

The way I know for finding the org.id is by running this:

bw list organizations

Thanks for your reply. It’s shown in the web frontend inside the organizations admin console → settings → organization information → show API keys.

It also shown in the browser URL after accessing the admin console.

I tried your approach, which actually shows zero organizations to me. I’m logged in with the master account of our organization.

Screenshot 2025-10-21 144201

Should I contact official Bitwarden support about this? Doesn’t seem to be right.

You’re right! I checked with my personal account (family org) and I don’t have the show api keys button there. I do on my work’s account (enterprise org).

I hadn’t noticed that! :sweat_smile:

That doesn’t sound right. If you belong to 0 organizations you should not have access to the admin console.

I would:

  1. Logout from the CLI
  2. Login again
  3. bw sync
  4. bw list organizations

And contact support if it still shows no organizations.

Thanks for your help! :grinning_face:

It was my mistake, I was on the wrong server. We are hosted on the EU server, but the default seems to be bitwarden.com. Running “bw config server https://vault.bitwarden.eu” before logging in solved the issue. I have no idea why I was able to login at the other server at all. Shouldn’t be possible imho.

Is there any way to permanently set the desired server without having to run “bw config server” before every login?

The only possible explanation is that there is an account with the same email, master password and one of your 2SV methods there.

I would bet that the chances that that hypothetical account was created by someone else are very low

Idk, perhaps try to login to it from the web vault to confirm it…

The last used server on the cli is stored on the data.json file.

So, you will need to configure it again only if you change it to log in to another server.

bw status will show you your currently selected server.

1 Like