Connecting to the vault…
The page is requesting the encrypted data. Nothing is decrypted before you enter the master password.
The data could not be reached yet. The page keeps trying.
No access to the vault
The vault has not been created yet, or your account does not have Contributor access to this artifact.
Ask whoever administers the vault for access and open the page again.
The vault key record is missing
There are encrypted entries, but the vault/meta record, which holds the vault key, is gone.
Do not create a new vault: the existing entries would become unreadable. Restore that record from a backup.Put the vault/meta.json file back in the repository by reverting the commit that removed it.
Create the vault
Choose the master password the team will share. A phrase of four or more words is easier to dictate and harder to guess.
Restore from a backup
Team credentials, encrypted before they leave the browser.
- One master password opens the vault. It is shared by the team and is not stored anywhere, not even on this page.
- Every entry is encrypted with AES-256-GCM on your device. Title, username, group and notes included: the databasethe git repository only ever receives ciphertext.
- The vault locks itself. After a few minutes without activity, or when the page is reloaded, it asks for the master password again.