Why assigning a secret to collection removes it from the main list instead of creating a symlink?
@horiz0n Welcome to the forum!
As explained in Bitwarden’s Security Whitepaper, shared items are encrypted using a key that is different from the user’s encryption key; this is the organization’s encryption key, which is then protected by asymmetric encryption using an RSA key pair specific to each organization member. Thus, there is a completely different infrastructure for encryption and decryption of shared item vs. your individual, non-shared items; therefore, having shared and non-shared items in different vaults makes sense.
In addition, my understanding is that the organization features were designed to meet the needs of business customers, who have passwords or other sensitive data that need to be used by multiple employees. Thus, the paradigm that was developed was to have a vault belonging to the organization (i.e., the company), and allowing users (i.e., employees) to access some defined subsets (collections) of the organization data. This was evidently not designed for peer-to-peer sharing.