Naming Every Account Owner Before the Question Comes Up
Most ecommerce stores do not lose track of their accounts all at once. The drift happens quietly. A former contractor still holds an admin login, a shared email address receives verification codes nobody reads, and the person who set up the payment connection has moved on. When a question finally arrives, such as who can approve a change or where a recovery code lives, the answer exists only in someone's memory. This article takes a different angle from a general inventory: it focuses on ownership, the people attached to each account, and the questions that expose gaps before they become emergencies. Nothing here assumes any particular platform feature or service level. It describes a method you can apply to any set of accounts you run.
Start With Ownership, Not Credentials
A common first instinct is to list usernames and passwords. That list is useful only after you know who is supposed to control each account. Begin with a simpler table: account name, the business purpose it serves, the named person accountable for it, and a backup person who could act if the primary is unavailable. Keep the actual secrets out of this document. The point is to answer the question of who decides, separate from the question of how someone logs in.
Ownership gaps show up quickly once you write this down. You may find an account whose accountable person is listed as someone who left two years ago, or a purpose that nobody can explain. Those rows deserve attention before any technical work begins, because an account without a clear owner tends to accumulate risk without anyone noticing.
Separate Access Records From Secret Storage
Access records describe what exists: which accounts you run, which devices or email addresses receive their verification messages, which people hold administrative roles, and when each role was last reviewed. Secret storage is the separate question of where credentials are kept and who can retrieve them. Mixing the two produces a document that is either too sensitive to share or too vague to act on.
A practical approach is to keep the access record in a shared, non-secret document that records the existence and ownership of each account, while storing actual credentials in a dedicated password manager or another controlled location your team has agreed on. Note in the access record where the secret lives, not the secret itself. That way a new team member can learn the structure without learning the keys.
Ask the Questions Before You Need the Answers
A good inventory is tested by questions. Work through these for each account and write down the answer, or write down that you do not know, which is itself useful information. Who can approve a payment method change? Which email address receives account security notifications, and is anyone monitoring it? If the accountable person became unavailable tomorrow, who could recover access, and what would they need to prove identity? Are any recovery codes stored only on one personal device? When was the last time someone confirmed these details were still accurate?
Unanswered questions point to specific fixes. An email address nobody reads needs a new owner. A recovery method tied to one device needs a second route agreed upon in advance. An approval step that depends on one person needs a named alternate. Treat each unanswered question as a task with an owner and a date.
Build a Simple Review Rhythm
Records decay unless someone reviews them. Choose a recurring interval that fits how often your accounts change, such as a quarterly review for a small store or monthly during a period of heavy growth. Each review should confirm that every account still has a current owner, that backup contacts are still reachable, that no departed person retains access, and that the purpose column still matches what the account is used for.
Record the date and the reviewer's initials in the document itself. A review log may feel like bureaucracy, but it answers a question future you will certainly ask: when was this last checked, and by whom?
A Practical Checklist for Your Next Review
Before closing your first review, confirm each of the following. Every account has a named owner and a named backup, both current. Each account's purpose is written in one sentence. The location of recovery information is recorded without the secret itself. Shared email addresses that receive security messages have an identified person responsible for reading them. Former team members have been removed from every administrative role they held. Any approval step that requires a specific person has a documented alternate. The review date and reviewer are noted.
Compare this list against a loose spreadsheet with no owner column, and the difference is clear. The spreadsheet records what exists. The ownership record records who answers for it and who answers when that person is absent. The second question is the one that matters most during a disruption, and it is the one most stores have never written down. Begin with the ownership column, ask the questions in the section above, and let the gaps you find set your priorities.