How should I securely hand over client credentials if I’m unavailable?
Asked by
MellowPine47
I provide occasional web development and general technical services for clients, often building their websites and managing the associated services while they stay out of the day-to-day work. I want a reliable contingency plan so a client can regain control if I become seriously unavailable, leave the relationship, or otherwise can't continue supporting them.
The credentials should be kept separate from my personal accounts, regularly updated, and protected from clients making impulsive changes while I'm still responsible for their systems. At the same time, they shouldn't be permanently locked out if something happens to me. I work alone and don't have a lawyer or trusted technical partner available to manage an emergency handover. What setup would be practical and secure?
Answers
Start with ownership rather than just password storage. The client should own the domain registration, hosting account, billing details, DNS, and primary account email wherever possible. Create a client-owned administrator account for them, then add your own separate delegated account with only the access you need. That way they can remove you or hire someone else without needing your personal credentials, and your password manager is only a backup for the few secrets you genuinely need to hold.
Reply to this answer
If you don’t trust anyone to manage a password manager account, use an offline escrow arrangement. Keep an encrypted password database on a USB drive in a fireproof safe, leave the unlock instructions in a sealed envelope, and replace the backup whenever important credentials change. The person holding it doesn’t need technical expertise, but they must be reliable and know exactly when they’re authorized to hand it over. The downside is that it requires a disciplined update process or the backup will become stale.
Reply to this answer
A password manager with emergency access can work well here. Give a carefully chosen trusted person access to a client-specific vault, set a waiting period such as seven days, and require them to request access before anything is released. You can cancel the request during the waiting period, which prevents casual or impulsive access while still providing a clear handover path. Keep each client in a separate vault or account so an emergency release does not expose everyone’s credentials.
Reply to this answer
You can also create a separate client emergency administrator account protected by a second factor that is stored separately from your normal equipment. Give the client the account name and password, but keep the security key or recovery method in a documented location that an authorized representative can access. Be careful with this approach: recovery codes, billing access, and account ownership still need to be documented, and a shared account is usually less auditable than individual accounts with delegated permissions.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions