Shared vaults Coming soon
The office password no longer travels by chat
Shared accounts exist: the supplier portal, the social profile, the management software. A shared vault puts them in one place, with clear roles and a list of members. And when someone leaves, you know what to change.
Who belongs, and with what role
At Studio Morelli, accounts staff use the same logins for the tax agency portal and clients’ tax records. You create the “Administration” vault, invite the three people who work there and give each a role. Every member receives the vault key encrypted for them, and membership is stated by acts signed by the managers, not by a list kept by the server. The vault name is encrypted: only members see it.
How it works
-
You create the vault
In “Shared vaults”, “New shared vault”: write the name and you become its manager.
-
You invite people
You search by name or email, choose the role and invite, one person at a time or a group. Whoever receives the invitation sees who sent it and who belongs, and decides whether to accept.
-
You compare fingerprints
The first time, you trust that a colleague’s key is theirs: Jinni presents it to you. If you want certainty, compare the fingerprint in person or by voice, not by email or chat.
Whoever could see a password still knows it: change it on the site
What you can do
-
Three roles
The manager does everything, the editor creates and edits entries, the reader views, copies and fills in. The reader has the vault key like the others: the server and the other members’ software stop their changes.
-
Invitations to check before accepting
Anyone can call a vault “Administration”. That is why the invitation shows who sent it, who created the vault and who belongs to it. If you are not convinced, you reject it.
-
If a colleague’s key changes
“Key changed” appears next to the name and Kamzan Pass stops: it encrypts nothing for that person until you compare the fingerprint with them. It may be a legitimate change, or someone impersonating them.
-
Removing a person
With “Remove and rotate the key” the vault key changes and goes only to those who stay. It does not make the person leaving forget anything: whoever could see a password still knows it.
-
The “To change” list
Credentials others could know end up here, with what needs changing: password, TOTP code or passkey. The row disappears only when the value is actually different, and your device computes the list.
-
Groups, with a confirmation
“Invite a group” sends an invitation to each person. Someone who joins the group later does not enter the vault automatically: a manager confirms it, seeing who added them, and they start as a reader.
Frequently asked questions
Can a reader copy passwords?
Yes: they view, copy and fill in, and whoever can read an entry can also export it, which cannot be prevented or reliably logged. A passkey in a shared vault belongs to all members, readers included. The role decides who edits, not who knows.
What happens when I remove someone?
The vault key changes and goes only to those who stay, and the passwords that person could see go to “To change”. They must really be changed on the sites: until you do, the person who left may still know them. If they have a copy on their device, they can read it until that device reconnects or the copy expires.
How do I know a colleague’s key is really theirs?
At first contact it depends on Jinni, which presents it to you; after that, any change is visible. For certainty, compare the fingerprint by voice or in person: if it matches, “The fingerprint matches” marks the colleague as verified.
Can an editor erase an entry’s history?
They can trash an entry and create it again from scratch, losing its history and marks. Who did it stays on record. That is why the editor role should go to people who really need to change entries.
The other Kamzan Pass features
Want to see it before it arrives?
We show you Kamzan Pass on a test vault: how a password is shared, what happens when someone leaves the company and what the server doesn’t see. Half an hour, no strings attached.
Alex