Heimlane Vault for teams, in 3 minutes

This is Alice. She leads a team. The team shares logins every day. Alice creates a Shared Vault for her team. Her browser generates a new Shared Vault key. Neither Heimlane nor anyone outside the team will ever see it. Alice's public key encrypts the Shared Vault key. The key will be stored securely, in encrypted form. Alice sorts the passwords into groups. Marketing, Finance, IT. Each item is encrypted before it leaves her computer. Only encrypted items are stored in the Shared Vault. Alice invites Bob with his work email. Bob accepts, and Alice grants him access to the Shared Vault. Alice's confirmation creates a copy of the key for Bob. It is encrypted with Bob's public key. Then sent to Bob, still encrypted. Only he can decrypt it, with his private key. David and Chloé join the team the same way. One vault, one key, an encrypted copy for each. Roles set who manages what. Owner, Administrator, Manager, User. Bob belongs to the Marketing and IT groups. He sees only those. Each group has its own settings. Read-only, hidden passwords or full access. Vault rules apply to every member… …and are simple to turn on. Chloé leaves the team. Alice removes her from the member list. Her copy of the key is deleted and her access ends. Every change is recorded in the audit log. The Heimlane platform keeps only encrypted items and keys. Zero knowledge, end to end. Alice, Bob and the whole team… …each with their own key. Everything is unreadable except to those who belong to the team.