# No organisations in android app

**URL:** <https://vaultwarden.discourse.group/t/no-organisations-in-android-app/1510>\
**Category:** Uncategorized\
**Created:** [March 18, 2022, 4:23am UTC](https://vaultwarden.discourse.group/t/no-organisations-in-android-app/1510 "2022-03-18T04:23:39Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![cksapp](https://avatars.discourse-cdn.com/v4/letter/c/b9e5f3/32.png) [@cksapp](https://vaultwarden.discourse.group/u/cksapp)\
**Post date:** [March 18, 2022, 3:22pm UTC](https://vaultwarden.discourse.group/t/no-organisations-in-android-app/1510/2 "2022-03-18T15:22:06Z")

</div>

Hello,

> [@LovesTha](#):
>
> I’ve added an organisation and added my wife to it. She accepted and then I approved her (is there a reason for a third step here?).

This is how things are handled with the upstream Bitwarden project and as such Vaultwarden tries to match the intended behavior expected from the server.  
The Org invite, and further the user acceptance is part of how the Org and user exchange encryption information, please see [Bitwarden Security White Paper](https://bitwarden.com/help/bitwarden-security-white-paper/#sharing-data-between-users) for more.

> **[Bitwarden Upholds High Security Standards with Annual Third-Party Audits |...](https://bitwarden.com/blog/third-party-security-audit/)**
>
> Bitwarden will continue to uphold high cybersecurity standards through annual third-party security audits of the Bitwarden product and service.

The third step of approving the user, I believe is a function added after the [2018 Security Code Assessment](https://cdn.bitwarden.net/misc/Bitwarden%20Security%20Assessment%20Report.pdf) regarding the vulnerability BWN-01-008

> Public key authentication via fingerprint (see #1 above) has been added to the confirmation step while  
> onboarding new users into an organization. Users can view and verify their fingerprint under their  
> account’s settings in various Bitwarden client applications. Going forward, we will continue to investigate  
> the possibility of implementing public key authentication for organization user onboarding in other  
> Bitwarden client applications, such as the desktop app, which are less susceptible to malicious server-  
> side attacks (see #2 above). This would make the authentication process of public keys returned by the  
> Bitwarden API server even safer.  
> Finally, it should be noted that users also have the ability to self-host the Bitwarden server on their own  
> trusted infrastructure which would remove the risks associated with this issue almost entirely.

As such this prompts the Org admin to confirm the users’ account fingerprint phrase to confirm the proper account is being accepting into the Organization.

* * *

> [@LovesTha](#):
>
> She can see the shared collection via the web interface. But she can’t see it in the android app, is there a setting I’m missing?

Can you confirm if she is able to see them in the main web interface of her “personal” vault or only when she going into the “Organization Vault” view?  
As long as she is assigned access to the Organization and the collections then those should show up in the personal vault and subsequently in the Android app.

If she is an Organization Owner or manager (I believe) then they will have access to the Organization and collections even if they are not “assigned” to the user to view, but will still not show up in the user’s personal vault view and the applications or browser extensions.  
Hope this info helps 🙂

---

_[View the full topic](https://vaultwarden.discourse.group/t/no-organisations-in-android-app/1510)._