Introduction
Freelancers handle dozens of client credentials: domain registrars, hosting accounts, CMS logins, social media, analytics, and more. Storing these in a Google Sheet or a text file is a security disaster waiting to happen.
This post shows you how to store and share client credentials safely.
The problem with plain text
- Google Sheets: Anyone with the link can see all passwords
- Text files: Easy to lose, share, or leak
- Email: Passwords in emails are searchable and stored forever
- WhatsApp: Messages are backed up to cloud
- Browser saved passwords: Shared if someone uses your computer
One breach = all clients compromised. Don’t risk it.
The solution: password manager
Recommended tools
| Tool | Price | Best for | Key feature |
|---|---|---|---|
| 1Password | $3/mo | Teams, agencies | Shared vaults, secure sharing links |
| Bitwarden | Free (personal), $4/mo (teams) | Budget-conscious | Open source, self-hostable |
| LastPass | Free (limited), $3/mo | Individuals | Easy to use, browser integration |
| Dashlane | $5/mo | Individuals | VPN included, dark web monitoring |
Recommendation: Bitwarden (free, open source) for solo freelancers. 1Password ($3/mo) for teams/agencies.
Step 1: Set up a password manager
- Create an account
- Install the browser extension and mobile app
- Set a strong master password (use a passphrase: 4-5 random words)
- Enable 2FA (authenticator app, not SMS)
Step 2: Create a vault structure
Organize by client:
📁 Vault: Freelance Clients
├── 📁 Acme Corp
│ ├── Domain Registrar (GoDaddy)
│ ├── Hosting (Bluehost)
│ ├── WordPress Admin
│ ├── Google Analytics
│ └── Social Media
├── 📁 StartupX
│ ├── Domain (Namecheap)
│ ├── Hosting (Vercel)
│ └── CMS (Webflow)
└── 📁 Shared Tools
├── Canva (team account)
├── Figma (team account)
└── Google Workspace (admin)
Step 3: Add credentials
For each client login, store:
- Name: “Acme Corp — WordPress Admin”
- URL: https://acme.com/wp-admin
- Username: [email protected]
- Password: (generated strong password)
- Notes: “Admin account. Client also has editor access.”
- Tags: acme-corp, wordpress, admin
Never store passwords in plain text. The password manager encrypts everything.
Step 4: Share credentials with clients (securely)
Method 1: Shared vault (1Password, Bitwarden)
- Create a shared vault for each client
- Invite the client (they create their own account)
- Both of you see the same credentials
- Revoke access when the project ends
Method 2: Secure sharing link (1Password)
- Generate a one-time link that expires after viewing
- Share via email (the link itself is safe to email)
- Link expires after 1 view or 24 hours
Method 3: Encrypted note (any password manager)
- Create a secure note with credentials
- Share the note via a secure link
- Client views it once, then it’s gone
What NOT to do:
- ❌ Send passwords via email (searchable, stored forever)
- ❌ Send passwords via WhatsApp (backed up to cloud)
- ❌ Store in Google Sheets (anyone with the link sees everything)
- ❌ Use the same password for multiple clients
- ❌ Store in browser saved passwords (shared if someone uses your computer)
Step 5: Generate strong passwords
Use your password manager’s generator:
- Length: 16+ characters
- Mix: uppercase, lowercase, numbers, symbols
- Unique: different password for every account
- Never reuse: if one account is breached, others are safe
Step 6: Enable 2FA everywhere
Two-factor authentication adds a second layer:
- Authenticator app (Google Authenticator, Authy, 1Password) — recommended
- SMS — better than nothing, but vulnerable to SIM swapping
- Hardware key (YubiKey) — most secure, for high-value accounts
Priority accounts for 2FA:
- Email (Gmail, Outlook)
- Password manager
- Domain registrar
- Hosting provider
- Banking/payment accounts
Step 7: Credential handover (project completion)
When a project ends, transfer credentials to the client:
- Create a handover document with all logins, URLs, and instructions
- Share via secure link (1Password sharing link or encrypted note)
- Change passwords if you had shared access (security best practice)
- Revoke your access (remove yourself from shared accounts)
- Document the handover (email confirmation that client received credentials)
Common mistakes
- Storing passwords in plain text — Google Sheets, text files, notes apps
- Reusing passwords — one breach compromises everything
- No 2FA — passwords alone aren’t enough
- Sharing via email/WhatsApp — insecure and permanent
- Not revoking access — old clients still have access to your tools
- No backup — if you lose your password manager, you lose everything. Back up the encrypted vault.
Key Concepts
- Password manager = encrypted vault for credentials
- Shared vault = credentials shared between you and the client
- 2FA = two-factor authentication (password + code)
- Secure sharing link = one-time link that expires after viewing
- Credential handover = transferring access to the client at project end
What to Try Next
- Organise client projects with a system
- Track domains and hosting for all clients
- Write SOPs for credential management
- Set up client onboarding for new projects
FAQ
Is Bitwarden really free?
Yes — Bitwarden’s free tier includes unlimited passwords, sync across devices, and basic sharing. The paid tier ($4/month for teams) adds shared vaults, 2FA, and priority support. For solo freelancers, free is enough.
What if I lose my password manager master password?
You lose everything. There’s no “forgot password” for password managers (by design). Write your master password on paper and store it in a safe place. Some managers (1Password) have recovery options via a family member or emergency kit.
Should I use a different password manager for personal and work?
No — one password manager with separate vaults is simpler and more secure. Create a “Personal” vault and a “Freelance Clients” vault. Use the same master password for both.
How do I share credentials with a team?
Use shared vaults (1Password, Bitwarden Teams). Create a vault per client or per project. Invite team members. When someone leaves, revoke their access. Never share master passwords or use shared accounts for sensitive systems. See Manage Multiple Clients.