What this guide covers
PassZit is a free, open-source (AGPLv3), self-hosted password manager for people and teams. Besides each person's own vault it has team vaults: shared vaults whose members and rights you choose. Sharing keeps the end-to-end encryption — the server never gets the key of a shared vault. This guide walks through setting up sharing for a team, from the first shared vault to the day someone leaves.
- What you need
- How sharing stays encrypted
- Make a team vault and set the rights
- Add people and groups
- Access that ends by itself
- Folders by customer, site or department
- Remote connections: RDP, SSH, WinBox
- Secret links and emergency access
- Approvals, item access log and audit log
- Company sign-in: LDAP and single sign-on
- When someone leaves
- Honest limits
- What to do next
What you need
- A running PassZit server — a ready-made VM image or one install command on Debian, Ubuntu, AlmaLinux or Rocky Linux. The guide Self-hosted password manager covers the installation; images and packages are on the download page.
- An account for every team member. Accounts are made only by invitation: an administrator opens Users → Invite a user, enters the e-mail address and the role and sends the invitation link. Each person chooses their own master password and sets up two-factor sign-in.
- A certificate that browsers trust (Settings → Certificate: your own, or Let's Encrypt). The browser extensions cannot connect to a server with the self-signed certificate it starts with.
How sharing stays encrypted
Every account has an X25519 key pair. A shared vault has its own random key, and every item in it is encrypted with AES-256-GCM in the browser. When you add a member, your browser seals the vault key to that person's public key; the server stores only the sealed copies and ciphertext. Administrators manage accounts and settings but, like everyone else, cannot read vaults they are not a member of.
Because the server hands out the public keys, PassZit shows a key's fingerprint the first time you share with a person. They see the same fingerprint under My account → Your key for sharing; compare it once, in person or by phone. PassZit remembers confirmed keys and warns when one changes. The details are on the security page.
Make a team vault and set the rights
- In the web vault, the list on the left starts with My vault, followed by Team vaults. Click the + next to Team vaults and name the vault — for example "Network" or "Marketing". You manage it.
- The gear next to its name opens Members and settings. There the rights of each person and group are check boxes.
- Create items in the vault, or move an existing item (with its files) with the Vault field of the item editor.
| Check box | May |
|---|---|
| Connect and fill | Open connections, fill and copy logins in the web vault and the extension — without showing passwords, notes or files. Every member has it. |
| See passwords | See everything in the vault. |
| Add and change | Also add, change and delete items. |
| Manage | Also members, groups, the name and the vault itself. |
A higher right includes the lower ones. A typical setup: the group Support gets Connect and fill and See passwords, the group Administrators also Add and change. The server refuses every change without the right, and a vault always keeps at least one permanent manager. If only administrators should make shared vaults, set it in Settings → Vault policy → Sharing and export; the same section can switch off exports.
Add people and groups
In Members and settings, Add a person takes a user, the right and, if you want, an end date. Confirm the fingerprint the first time, as described above.
For more than a handful of people, use groups. Administrators make them under Groups and choose the members; a vault manager then adds the group in the vault's settings and ticks what it may do — the same check boxes as for a person. Because the server cannot seal keys, a manager's browser gives the access: at once when the group is added, and for new group members the next time a manager opens the vault. Leaving a group ends its access at once. Groups can also follow the company directory or the identity provider (see Company sign-in).
Nobody can change their own access — another manager does it.
A vault always keeps a manager: if its only managers manage it through a group, PassZit refuses to take them out of the group or to delete the group until the vault has another manager. A change from the company directory still happens; it is written to the audit log and the administrators get an e-mail.
Access that ends by itself
An end date ends a person's access at the end of that day — useful for an external technician or a project. The audit log records the end.
Under Tools → Access requests anyone can ask for access, with a reason and a duration from 1 hour to 30 days:
- More rights in a team vault you are already in — any manager of the vault can approve. The rights go up at once and come back by themselves at the end.
- Access to a vault you are not in — you ask a manager or an administrator, who chooses the vault and clicks Give access. When the time is up the access ends and the vault gets a new key.
Whoever decides gets a number next to Access requests and an e-mail if the server sends mail. Requests nobody decides end after 7 days. Because nobody can change their own access, temporary rights cannot be made permanent by the person who holds them.
Folders by customer, site or department
Folders belong to a vault, and everyone with access to a team vault sees its folders. A folder has a kind with its own icon: Folder, Customer, Site, Branch office, Department, Data center, Network or Project. Folders can be nested, so an IT team can keep one folder per customer with a folder per site inside; below a customer, PassZit suggests a site. Folder names are encrypted like everything else about an item.
Search looks through the open vault in your browser; the button in the search field searches all your vaults and shows each result's vault and folder.
Remote connections: RDP, SSH, WinBox
A login can also be a remote connection. Choose Remote Desktop (RDP), SSH with a password, SSH key, WinSCP (SFTP), WinBox (MikroTik), VNC or Telnet under New item and fill in Remote connection: the program, the address and, if needed, the port.
A browser may not start programs, so the small MaxZit Launcher for Windows does it. Download it under Launcher in the web vault's menu — it installs for your Windows user without administrator rights — and pair it once per browser with Pair this browser. On Linux, the release has passzit-helper for the same job. A double-click on the item, or the terminal button in the extension, then opens the connection with the stored login, without typing the password.
In a team vault every member may open connections (Connect and fill), so a support technician can connect to a server without being shown its password. Each connection is recorded in the item's access log as "connected with it".
Secret links and emergency access
Secret links (under Tools, or Send a copy in an item) give one person a text or a file of up to 8 MB without an account. Choose how long the link works (1 hour to 30 days) and how often it can be opened (1–100 times, once by default). The content is encrypted in your browser and the key is the part of the link after #, which browsers never send to a server. An optional password protects the link a second time; tell it over another channel. After the last allowed opening the server deletes the data, and Delete stops a link at once. Recipients outside your networks must be able to reach the server.
Emergency access (under My account) names up to five people who may open your personal vault if something happens to you, each with a waiting time of 0–90 days (7 by default). If you do not reject their request within that time, they can read your personal vault, read only. Shared vaults are not part of it — they have their own members.
Approvals, item access log and audit log
- Four-eyes principle (Settings → Vault policy): sensitive administrator actions — deleting a user, resetting a second factor, making or inviting an administrator, changing the vault policy, sign-in, network and company sign-in settings — wait under Approvals until a second administrator approves them. Requests end after 24 hours, nobody approves their own, and it takes effect with at least two active administrators.
- Who used this item: in team vaults the web vault, the extension and the command line report when someone shows a password, copies a secret, fills a login, opens a connection, changes the password or restores a former one. Vault managers see who, when, from where, the device and the IP address.
- Audit log (administrators): sign-ins, failed attempts, blocks, invitations, user and settings changes, requests, approvals and the end of temporary rights. Every entry contains a hash of the previous one, and the page shows whether the chain is intact. The log never contains passwords or item contents.
Company sign-in: LDAP and single sign-on
Settings → Company sign-in connects PassZit with the company's accounts:
- Single sign-on with OpenID Connect (Microsoft Entra ID, Google, Okta, Keycloak …) or SAML 2.0 (ADFS, Entra ID, Okta …). The identity provider confirms the address, then the user enters the master password.
- Active Directory / LDAP: at every sign-in, also of extensions, PassZit looks the address up with a service account; missing or disabled accounts cannot sign in. Look up tests the settings.
Both can keep PassZit groups in step with company groups of the same name at every sign-in, so vault access follows the directory. The master password always stays — it is the key to the vault — and accounts still come only by invitation. Browser extensions cannot use single sign-on; they sign in with the master password and the authenticator code.
When someone leaves
- Stop the sign-ins. On the user's page in Users, tick Disabled (cannot sign in; open sessions end). With Active Directory / LDAP connected, disabling the account in the directory also stops PassZit sign-ins, including those of the extension and the command line.
- Remove the access. Remove the person from the team vaults and groups, or delete the account with Delete the account.
- Give the vaults a new key. Someone who leaves a vault still knows the old vault key, so PassZit replaces it: at once when a manager removes the person in the browser, otherwise the next manager who opens the vault sees Replace the key now. The browser encrypts every item again with the new key.
- Change important passwords. What the person saw before cannot be taken back. Who used this item shows which passwords they showed or copied.
Honest limits
- Connect and fill without See passwords is a convenience, not a lock: whoever can fill a password into a page can find it out with some effort.
- The item access log is reported by the browsers. Someone who changes their software can avoid it — it helps against mistakes and answers "who had it", it is not proof.
- Sharing trusts the server for the list of people. People who join through a group get access without a fingerprint confirmation by the manager.
- The web vault's JavaScript comes from your server; someone who fully controls the server could serve changed code. The browser extensions bring their own code. Protect the server like any other critical system.
- WinBox accepts the password only on its command line, where other programs of the same Windows user can read it while WinBox runs; PassZit warns before. The MaxZit Launcher is for Windows; on Linux use
passzit-helper. - Nobody can reset a forgotten master password, not even an administrator. Without a recovery key the account can only start again with an empty vault.
What to do next
- Install the browser extension for every team member and import existing passwords — see features and the documentation; the built-in user guide has a chapter on shared vaults and groups.
- New to PassZit? Start with Self-hosted password manager and the download page.
- Read how the encryption works on the security page.
Questions and ideas are welcome in GitHub Discussions (English only). MaxZit offers commercial support and onboarding for teams that want help.