Sorting Ecommerce Account Details by Access Level: A 2SOLV Approach

2SOLV editorial ·

Abacus used at State Department Store in Ulaanbaatar from 1923 to 1970.
Illustrative image. K.F. · CC BY-SA 4.0 · Cropped and resized. Image source

Most ecommerce owners do not lose track of their accounts all at once. The drift happens gradually: a login gets shared in a chat thread, a recovery email changes hands, a former contractor keeps a copy of a password sheet nobody remembered to retire. 2SOLV readers who are building or supporting online stores often find that the hardest part of running a marketplace business is not the selling itself but knowing, at any given moment, who holds which keys and whether those keys still belong with them. This article offers a method for sorting account details by access level, a way of thinking about records that puts the people who need information in front of the information they need, and a set of questions to ask before the next handoff. Nothing here describes a feature of any product or service. It is a general approach that any team can apply with whatever tools it already uses.

Start With Categories, Not Credentials

When people first try to organize account information, they usually begin by listing logins. That approach produces a long, flat document that mixes urgent items with trivial ones and gives no sense of who should see what. A better starting point is to sort the information into categories based on its sensitivity and purpose. A reasonable set of categories for a small ecommerce operation might include identity and ownership details, marketplace account access, payment and banking references, shipping and fulfillment accounts, advertising and analytics access, and communication channels such as shared inboxes.

Within each category, separate what the business owns from what individuals hold on its behalf. A marketplace account belongs to the business, but the person who set up two-step verification may be the only one with the phone that receives the codes. Recording that distinction changes what a recovery plan has to look like. The goal at this stage is not perfection. It is to create a skeleton where every piece of information has a home and a stated purpose.

Assign Access Levels Before You Write Anything Down

Once the categories exist, assign each item an access level. A simple three-tier model works well: owner-only items that only the business principal should see, operational items that a trusted manager or assistant needs to do daily work, and reference items that a support contractor might need for a specific task and then no longer. The tiers matter because they determine where a detail can safely live. An owner-only item should not sit in a spreadsheet that a dozen contractors can open.

Ask for each item: who needs this to do their job, how often do they need it, and what happens if they no longer have it? If the honest answer to the last question is that nothing bad happens, the item may not need to be stored centrally at all. Access that no one uses is a liability waiting to be exploited, and reducing it is often the single most useful step a team can take.

A Checklist for Each Category

Work through each category with a short list of plain questions. For marketplace access, ask which people have administrator rights, whether any shared logins remain, and whether the recovery contact information still reaches someone currently on the team. For payment references, ask whether the people who can change payout details are the same people who approve them, and whether anyone outside the business can see the bank references. For communication channels, ask who receives notifications, whether the forwarding addresses are current, and what happens to messages when a team member leaves.

Record the answers in a single place the owner controls. The record does not need to contain secrets. It can instead describe where each secret is kept, who holds it, and when it was last reviewed. A line such as 'Marketplace seller login: held by owner, password manager vault, reviewed in March' is far more useful than the password itself in a shared document.

Compare Two Ways of Storing the Same Information

Consider two operators who both run a modest store. The first keeps a single shared spreadsheet with every login, recovery code, and phone number, visible to all four contractors who help with listings. The second keeps an index sheet that lists each account, its owner, its access level, and the location of its secret in a dedicated password manager, with only the owner holding the vault key. When a contractor's engagement ends, the first operator must assume the spreadsheet has been copied and change everything. The second operator removes one person's access and confirms that nothing else was exposed.

The second approach takes more setup time, but it converts a crisis into a routine task. The difference is not that the second operator is more careful by nature. It is that the structure of the records makes the careful action easy to take. That principle is the core of organizing account information well.

Questions to Ask Before the Next Handoff

Before any team member leaves, joins, or changes responsibility, run through a short set of questions. Which account details did this person touch in the last ninety days? Which of those details can be rotated without disrupting live operations? Who else should be notified that access is changing? Is there a second person who knows how to reach the marketplace support process if the primary contact is unavailable? Does the index sheet reflect the change, and has someone other than the person making the change confirmed it?

These questions are not a legal or financial checklist, and they do not replace advice from qualified professionals when a situation involves significant money or regulatory obligations. They are a way to keep ordinary operational records honest. A team that asks them regularly will find that its account information stays tidy, its handoffs stay smooth, and its owner sleeps a little better knowing that the business does not depend on any single person's memory.