← Back home

Teams & access

What to do when a marketplace asks you to verify a new team member

Your marketplace wants to check a new team member before they can work on your seller account. Here is what it checks, what to prepare, and how to add them without a hold or a lockout.

A business owner showing a new team member a marketplace dashboard on a laptop

Why this guide exists

Hiring your first helper is a good sign — the business has grown enough to need one. But the first time a marketplace asks to verify that person, most sellers are caught off guard: they expected a simple invitation, not an identity check. This guide walks through the whole process in order, so a routine step stays routine and your team can start work on schedule.

Why marketplaces verify team members at all

When you hire someone to help with listings, customer messages or fulfilment, your marketplace does not just hand them the keys to your seller account. Most marketplaces ask the new person to verify their identity first — sometimes with a government ID, sometimes with a short confirmation step — before they can work inside your account. If you have never added a team member before, the request can feel like an obstacle. It is not. A marketplace does not verify a new team member to slow your business down — it verifies them so the account stays yours when the team changes.

The reason is simple: a seller account is a trust record. It holds your sales history, your payout details, your customer messages and your reputation with buyers. If anyone could log in as a team member with no check at all, a stolen password or a dishonest hire could change payout details, message customers or damage that record in an afternoon. Verification ties each person who touches the account to a real identity, so the platform can tell the owner apart from the team — and so you can prove later who did what.

There is also a practical side. When a dispute, a refund or a security review comes up, the platform checks the people on the account first. A team member who has been verified in advance is never the reason a review drags on.

What the platform usually asks for

The exact steps differ from one marketplace to another, but the pattern is the same on almost every platform: the owner sends an invitation from the seller dashboard, the new team member accepts it, and the platform asks them to confirm who they are.

  • A government-issued photo ID — a passport, driving licence or national ID card. The name on it should match the name the person uses on the account, letter for letter.
  • A work email address the team member controls. Avoid free personal inboxes for this step; a business email tied to your domain is cleaner and easier to recover later.
  • A phone number that can receive a confirmation code. The number should belong to the team member, not to you, because it becomes their recovery route.
  • A short confirmation of their role — what they will actually do on the account, such as listings, customer service or fulfilment. Some platforms ask the owner to pick a role from a list.
  • Occasionally, a selfie or a short liveness check, where the person confirms they are the person on the ID. This is the same kind of check many platforms already use for the account owner.

Before you start: gather these five things

Most verification delays are not caused by the platform. They are caused by starting the process before the details are ready. Ten minutes of preparation before you send the invitation saves days of back-and-forth, because every mismatch between what the platform holds and what the team member submits can pause the review.

  • The team member's full legal name, exactly as it appears on their ID — not a nickname, not a shortened first name, not the name they use on social media.
  • The email address they will use for the account, already set up and tested, so the invitation does not sit unread in an inbox they never check.
  • A clear photo or scan of their ID, with all four corners visible, no glare and no cropped edges. A photo taken in daylight against a plain surface usually passes first time.
  • The role you want them to have, decided in advance. If you are unsure, start with the smallest access that lets them do their job — you can always raise it later.
  • A note of the date you sent the invitation. If the review takes longer than the platform's usual window, that date is the first thing support will ask for.

The step-by-step process

The flow is straightforward once you have seen it once. The owner starts it, the team member completes it, and the platform confirms it — three actors, one short sequence. Walk through it in order and resist the urge to skip a step, because each step protects the next one.

  • Open your seller dashboard and find the team or users section. Send the invitation to the team member's work email and pick their role before you send it.
  • Ask the team member to accept the invitation from that email, not from a forwarded copy. Forwarded invitations are a common reason the accept step fails.
  • The team member completes the identity check the platform shows them, using the ID and phone number you prepared together. They should do this on their own device, on a connection they normally use.
  • Wait for the platform's confirmation. Some checks finish in minutes; others take a day or two while a person reviews the documents. Do not send a second invitation while the first is still being reviewed.
  • Once the confirmation arrives, sign in together and check what the team member can actually see and do. If a permission is missing, adjust the role now — before their first shift, not during it.

Set the right access level

The most important decision in the whole process is not which document to send. It is how much access the new person gets. Every marketplace lets you choose a role, and the roles exist for a reason: the person packing orders does not need to change payout details, and the person answering customer messages does not need to see your bank information. Give each person the smallest set of permissions that lets them do their job well, and nothing more.

Start with a simple rule: if a permission lets someone move money, change who gets paid, or hand the account to someone else, it belongs to the owner only. Listings, orders, messages and inventory are working permissions; payout settings, bank details and the ability to add other users are owner permissions. A new team member who asks for owner-level access on day one is asking for something they do not need, and a careful owner says so plainly.

Write the role down in your own records too — who has which role and when it was set. Review the roles every few months, especially after someone's job changes. Access that made sense at hiring often stops making sense a year later.

What can go wrong — and how to fix it

Most team-member verifications go through cleanly. When one does not, the cause is usually small and fixable — a detail that does not match, a document the platform cannot read, or a step done in the wrong order.

  • Name mismatch — the name on the invitation and the name on the ID differ by a letter or a spelling. Fix it by correcting the invitation to the legal name and asking the platform to re-check, rather than editing the ID details.
  • Expired or unreadable ID — the document has passed its expiry date, or the photo is blurred, cropped or covered by glare. A new, clear photo of a current document usually clears the review.
  • Invitation sent to the wrong email — the team member never receives it, or it lands in an inbox they do not use. Cancel the first invitation and send a fresh one to the correct address.
  • Duplicate account flag — the platform notices the team member already has their own seller account with the same details. Ask support how the platform wants the two accounts linked, and do not create a second identity to work around it.
  • Review taking longer than expected — the check is still in a queue, or the platform needs one more document. Wait for the platform's stated review window before chasing, then contact support with the invitation date and the team member's name.

When verification fails or stalls

A failed verification is frustrating, but it is rarely the end of the road. The first step is to read the platform's message in full — it usually names the problem, even if the wording is vague. A message about a document problem means the document; a message about identity means the details do not match what the platform holds. Fix the thing it names, not the thing you assume it means.

If the platform gives you no reason, contact support with the facts in one message: the account name, the team member's name, the date you sent the invitation, and exactly what the platform showed when the check failed. Keep the case reference the platform gives you, and reply in the same thread if you are asked for more.

Two things you should never do while a verification is stuck. Do not create a second account for the team member to work around the check — the platform will see two identities for one person, and that creates a bigger problem than the one you started with. And do not share your own login with the team member so they can work while you wait. The moment someone else uses your login, the platform can no longer tell who did what on your account, and a security review will treat every action as yours.

Keep the team list tidy

Adding a team member is only half the job. The other half is keeping the list of people on your account accurate as the team changes. When someone leaves, remove their access the same day they leave — not at the end of the week, not when you remember. A former team member who can still log in is a risk you chose to keep, and it is one of the easiest risks to remove.

Set a simple routine: once every few months, open the team section of your seller dashboard and read the list. Is every name on it still working with you? Does each person still need the role they have? A five-minute check every quarter keeps the list honest.

Finally, remember that verification is a one-time step, not a permanent pass. Platforms can ask a team member to re-verify if something changes — a new device, a new location, a long gap since they last logged in. That is normal, and it is a sign the checks are working. Treat a re-verification request the same way you treated the first one: calmly, with the documents ready, and through the platform's own screens — never through a link in an unexpected message.

Verification requests to treat with suspicion

  • An email or message asking the team member to verify by clicking a link — real platforms run verification inside your seller dashboard, not through links in messages.
  • A request for a password, a full bank account number or a one-time code sent by chat or email. No genuine verification asks for these.
  • A message that creates urgency — an account will be closed today unless someone verifies now. Urgency is the oldest pressure tactic there is.
  • A sender address that looks almost like the marketplace's domain but is not quite right — one letter different, or a different ending.

Verify before you share

Every person on your account should be verified in advance — never share your own login to save time.

Least access first

Start each team member with the smallest role that lets them do their job. Raise it later if the work grows.

Remove promptly

When someone leaves, remove their access the same day. A tidy team list is a safer account.

Growing your team the safe way?

Every verified account in our catalog comes with clear team and access guidance, and support that answers verification questions in plain language. Ask us anything before you order.

This guide is educational only and is not financial, tax or legal advice. For questions about your own records, speak to a qualified professional.