Your documentation tool knows the password. Does it know the owner?
Most MSPs hear 'digital asset register' and think: we have that — it's called IT Glue (or Hudu). And for the question those platforms were built to answer, they're right. A technician at 2 a.m. needs the firewall credentials, the ISP account number, the M365 admin login: documented, structured, one search away.
But watch what happens when the question changes from *how do we get in?* to *who actually controls this?* — the client's founder asks who owns their domain, or an employee resigns and someone asks what walks out the door with them. The documentation platform holds the password and goes silent on everything that matters next.
Two different questions
Documentation is operational: credentials, configurations, runbooks — written by technicians, for technicians, so that work can happen. Its subject is *access*.
An ownership map is a governance layer: which legal or personal identity anchors each account, who the platform considers owner versus admin, where the recovery paths and billing point, and which human's departure orphans what. Its subject is *control* — and knowing a password tells you almost nothing about it. The password to a Shopify store owned by a departed co-founder's personal email is documentation of a problem, not control of an asset.
Where the documentation layer goes quiet
- Owner vs admin: the vault says you can log in; it doesn't say the agency is still the Google Business Profile's primary owner.
- Recovery paths: resets and 2FA flowing to a personal phone are invisible to a credential record — until they're the only thing that matters.
- Departure blast radius: 'show me everything Priya can touch' isn't a query a password vault answers; it's the first question after every resignation.
- The client-facing conversation: you can't put a credential export in front of a founder. Ownership, scored and ranked, is a deliverable they'll actually read — and pay for.
The layers work together
This isn't a rip-and-replace argument — keep the documentation platform; it's doing its job. The continuity register sits above it: client-facing where documentation is internal, control-focused where documentation is access-focused, and revenue-generating where documentation is a cost of delivery. In practice they even feed each other — the review surfaces accounts your techs never documented, and your documentation accelerates the review's interview stage.
The commercial difference is the point: nobody's client ever paid for their IT Glue entry. The ownership review, scored and branded, is a line item — the same knowledge, rotated to face the customer.
The free scan maps your domain, email, cloud, social and tools from public records — and shows what you'd lose access to tomorrow. No login, nothing to install.
Check my business