Home / Ongoing Work / Audits, Reports & Documentation / Credentials & access inventory document

We compile a reference document listing every access point to your site and its related services — hosting, domain registrar, WordPress admin, FTP, third-party accounts — and how to obtain or use each, for continuity if you or a new team member ever needs to find this in one place.

DOC-002

Credentials & access inventory document

Every access point to your site and its services, listed in one place for continuity.

$41.53 delivered in 48 hours
Needs WP admin login and Sub-account invite. Create a limited sub-account — we never ask for your own password.
  • Full backup taken before we start
  • If we can’t fix it, you get your money back
  • We never ask for your own password
Why this costs $49. An hour of a capable WordPress developer’s time runs about $82 in the UK, $100 in the US and $105 in the Gulf, and for anything urgent a two-hour minimum is normal. This is $49 for up to 45 minutes of hands-on work, with a full backup taken before we start. 2026 market rates.

What we need from you

  • Confirmation of every service and account that should be included
  • Your preference for how sensitive credential details are actually stored and shared
  • Confirmation of who should have access to the finished document

This or something else?

You want a reference document listing your access points for continuity purposes This fix covers it
You want a security-focused audit flagging risky access (shared passwords, stale accounts) SaaS account audit & access inventory report, in the Integrations & Automation bucket, the security-audit version
You want your own WordPress user accounts specifically audited Dormant admin account audit & removal, in the Security Hardening & Audit category
You want this as part of a full developer onboarding bundle Onboarding pack for incoming developer

What we do

  1. Confirm every service and account that should be documented
  2. Compile what each is for, where to access it, and any relevant notes
  3. Structure sensitive credential handling according to your stated preference
  4. Organise into a clear, usable reference
  5. Review for completeness against what you’ve confirmed

What is included

  • A reference document listing your access points and services
  • Notes on what each is for and how to access it
  • Sensitive details handled per your stated preference
  • A completeness review

Not included

  • A security audit flagging risky or shared-password access — a separate, security-focused report
  • Auditing your own WordPress user accounts specifically — a separate, related report
  • Actually changing or securing any access found — a separate, related fix
  • Ongoing updates as access changes over time

Questions about this fix

Is this the same as the security-focused access audit?

No — that report specifically flags security risk (shared passwords, stale access) with recommendations; this is a straightforward reference document for continuity, listing what exists and how to use it.

How should sensitive credentials actually be stored in this document?

We'd follow your stated preference — some businesses want actual credentials included in a securely shared document, others prefer references to where credentials are stored (like a password manager) instead.

Who should have access to this once it's created?

Whoever you specify — given the sensitive nature of the content, it's worth being deliberate about who actually receives it.

Will this flag if some of my access is set up insecurely?

Not as the primary purpose — if you want that specific security lens, the dedicated audit report is the better fit; this document is about completeness and continuity, not risk assessment.

Does this need updating as passwords change?

Yes, this reflects access as of when it's compiled — keeping it current as things change would need periodic updates.

Credentials & access inventory document
$41.53 · delivered in 48 hours · needs WP admin login, Sub-account invite

Related fixes

If this is the second time this year

A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.

See care plans

Your access, your rules

Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.

We back up first, always

Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.

If it is not what you bought

If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.

If we cannot fix it

You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.

If it comes back

Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.

What we are responsible for

If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.