Passwords
Shared logins still live in a browser, a 'passwords' sheet, and a Slack DM. Recovery codes and 2FA details are on a phone that left with an employee, so a vendor lockout becomes a week of downtime.
Hypervault stores service name, username, password, URL, and 2FA recovery in an encrypted EU vault, with permissions and a named owner so shared logins are not tribal knowledge.
Why store Passwords in a digital vault
The sheet is older than the last rotation
Logins fail and people reuse personal passwords. Last rotated on the vault item is the hygiene metric.
2FA is on one person's device
When they leave, the account is locked. Two-factor and recovery information belong with the password item.
URL is missing so people hit a phishing clone
The real login URL on the item is what the team should open.
Nobody owns the shared mailbox login
Owner/team makes rotation and offboarding a named job, not a guess.
Who uses this template
Every team with shared logins
Keep username, password, URL, and 2FA recovery in the vault instead of a sheet.
IT and security
See owner and last rotated across services without collecting browser exports.
Small companies without a dedicated IAM tool
Put the company password book in an EU vault with permissions, not a founder spreadsheet.
Fields in this template
Keep every record complete and easy to find. Existing fields stay as they are; extras are added only when a vault item would otherwise be incomplete.
- Service/Application name
- Username
- Password
- URL
- Notes
- Two-factor authentication
- Recovery information
- Owner/team
- Last rotated
How it works in Hypervault
Create from the template
Add an item from the Passwords template in your workspace.
Fill and attach
Complete the fields and attach supporting files where needed.
Share with the right roles
Give access only to the people who maintain or use this record.
Related templates
Penetration test reports
Template for storing penetration test results, security assessments, and vulnerability reports.
Security procedures
Template for documenting security procedures, protocols, and incident response plans.
Thread models
Template for documenting threat models, risk assessments, and security threat analysis.
Store it in a vault, not a spreadsheet
Create a workspace, pick this template, and keep credentials and supporting files encrypted in the EU.