Blog / Web management /
How to document access without putting credentials in a handover
The handover document is gloriously thorough. Hosting provider, domain account, and the password for each, ready for anyone with the shared link.
That’s not thoroughness, it’s a leak waiting to happen. The next maintainer needs to know where access lives, who owns it and how to get permission. They don’t need every secret sitting in a document that gets copied, emailed and kept long after access changes.
I document the route to access, never the credential itself. It makes the handover more useful too, because ownership and recovery still make sense after the password changes.
Build an account map
List the services required to operate the website: CMS, hosting, registrar, DNS, analytics, email-related tools, integrations and any source repository. Include the business purpose and accountable owner for each.
Separate the person who pays for a service from the person who administers it. They’re sometimes the same, often not. When I pick up a site, the first thing I ask is who can approve access and who gets the renewal notices.
Use recognisable names and a verified service address. Private project nicknames aren’t enough on their own. Someone dealing with an incident should be able to match the entry to the service they’re trying to reach.
Point to the approved credential system
Record where the authorised team manages access, using the organisation’s normal method. The handover can identify a vault entry, an account owner or a request process without copying the password or token.
Keep recovery material under the same deliberate control. Recovery codes, private keys and integration secrets are not ordinary explanatory notes. Identify who manages them and how an authorised person can reach them when needed.
A link to a secure system doesn’t prove the next maintainer can get in. Have them follow the approved process and confirm they can reach the entry. The route should work in practice, not just in the document.
Describe permissions and purpose
State which role the maintainer needs and what work it supports. Reading analytics, editing content and changing DNS are different jobs. “Use the admin account” hides that.
Where a service supports individual accounts or delegated access, use that instead of passing around a personal login. Check the permission model on the actual platform. Similar role names don’t mean identical powers.
Include temporary access where relevant. Say when it expires or which event triggers removal. A handover is a useful point to review old vendor access, provided the team checks dependencies before revoking anything that runs an important connection.
Separate instructions from sensitive values
A maintenance procedure may need to explain how an integration is configured. Describe the relevant setting and where its secret is stored, using a clear placeholder in the instructions. Do not paste a live key into screenshots or sample configuration.
Review existing screenshots too. Account names, customer information and recovery details can be visible in corners that the author did not intend to share. Keep only the detail needed to explain the task.
I also check attachments and older versions before sending a handover out. Deleting a password from the visible page doesn’t fix a copy already shared elsewhere. If a credential was exposed, replace it through your organisation’s process.
Document recovery and emergency access
Name who can help if the usual owner is unavailable. Confirm the provider’s verification process and who in the organisation can authorise a change. A phone number is handy, but it doesn’t give the caller authority over an account.
Think about dependency failures. If the website is unavailable, can the team still reach the handover and the credential system? If the usual email account is inaccessible, what approved recovery route remains?
These questions need practical answers from the owners. Avoid inventing an emergency workaround during the handover. Document the approved route and assign any missing arrangement as a task with a responsible person.
Rehearse the handover safely
Ask the incoming maintainer to find a service, identify the owner and obtain the access needed for a routine task. Let them use the document without coaching. Their questions show where the explanation is incomplete.
Check that they can distinguish reading access from change authority and know where to request more. The rehearsal should not require a live infrastructure change just to demonstrate that the instructions make sense.
Finally, update ownership and remove obsolete references once the transition is accepted. A handover that still directs people to the departing maintainer has not finished its job. Give the remaining team responsibility for keeping the account map current as services and roles change.
Keep a separate list of unresolved access questions. An account with unclear ownership shouldn’t hide among confirmed entries, where the incoming maintainer may assume it’s ready to use. Record the service, the missing decision and who resolves it. If it matters for recovery, tell the business owner before the handover is accepted.
Related reading
- Client website handover documents: what I include
- A process for reviewing vendor access to a website
- How to document recurring website maintenance decisions
Open your website handover and look for places where a secret has replaced clear ownership. Could an authorised maintainer follow the route without those values written down?