Academy›Special courses: eight courses for day-to-day selling›User permissions and account security: who can do what, and how to keep attackers out
Special courses: eight courses for day-to-day sellingTeam & processes

User permissions and account security: who can do what, and how to keep attackers out

Course lesson 1/3 ⏱ ~13 Min. 🏅 up to 215 points By Enes Kurt Updated November 2026 Check your listing free →
What you'll take away

An Amazon account has many doors: the sign-in, the mailbox, the phone that receives codes, connected apps, the advertising console, plus employees and service providers. Attackers do not look for the strongest door but for the forgotten one. In this lesson you learn to grant access sparingly, secure sign-in, review apps and spot an account takeover before the money is gone. Suspensions by Amazon itself are covered in account health, attacks on your listings in defending attacks.

1

One account, many people: the basic principle

Seller Central knows three kinds of access, each with its own purpose:

AccessFor whomWhat it can do
Primary userThe account owner, meaning youEverything, including bank details, permissions and account settings
Secondary userYour own employeesExactly the areas you grant, with their own sign-in
Authorized partnersOutsiders such as agencies, accounting firms or freelancersOnly the roles Amazon has vetted the provider for and that you confirm

One rule sits above everything: a sign-in belongs to exactly one person. Amazon explicitly does not support several people sharing one sign-in. Hand out your password and codes and you no longer know who changed what, and in an emergency you cannot block a single access. External providers register in the Solution Provider Portal, get verified and approved for specific roles; you then confirm them under Settings, User Permissions, in the “Authorized Partners” tab. How to hand work to outsiders without sharing credentials is shown in handing off tasks.

In plain terms

Your account is an office building, and you hold the master key. Employees get a key card that opens only their doors and remembers who passed through and when. Outsiders get a visitor badge checked in advance. What you never do: copy the master key and hand it around. Then you no longer know who was inside, and if one copy goes missing you have to change every lock.

2

Granting user permissions

Under Settings, User Permissions you invite a secondary user by email. The person creates their own sign-in, with an email address that does not already belong to an Amazon account. You then set a level per area:

LevelMeaningTypical use
No accessThe area is invisibleEverything the person does not need for their task
ViewRead without changesReports for accounting or analysis
View and editRead and changeThe area the person actually works in
AdminFull rights, including over other users’ rightsOnly your own sign-in and at most one deputy

The principle is called least privilege: as little as possible, as much as necessary. Start with “no access” everywhere and grant selectively. Three areas always stay with you, because a mistake there costs money or the whole account: granting permissions, bank and payment details, and account and legal information. For the usual roles it looks like this:

RoleEditView onlyNo access
Customer service (secondary user)Buyer messages, returnsOrdersPrices, inventory, advertising, payments
Advertising (advertising console user)Campaigns, bids, budgetsAdvertising and search term reportsSeller Central, unless needed
Accounting (authorized partner)nothingSettlement, payment and tax reportsOffers, messages, advertising
Owner (primary user)everythingeverythingnothing; solely responsible for bank details, permissions and account information
Example

The seller behind the AURELO spice grinder set (€24.99) hires a part-time customer service assistant. She gets “view and edit” for buyer messages and returns, “view” for orders and “no access” everywhere else. When she asks whether she may “quickly” fix a price, the answer is: she reports it and the owner changes it. That costs two minutes and spares everyone the question of who set the price to €2.49 on a Sunday.

The advertising console and Brand Registry manage their users separately, with their own roles. Removing someone’s rights in Seller Central does not remove them there. So keep an access list with three columns: person, system, level.

3

Revoking access and reviewing it regularly

Access is granted quickly and rarely collected again. Two routines stop former temps and ended agencies from keeping their rights:

  1. On the last working day: remove the access in Seller Central, the advertising console and Brand Registry, change shared passwords of other tools, check mailbox forwarding rules. The same day, not “soon”.
  2. Once a quarter: compare your access list with the actual users in all three systems. Whoever is no longer needed is removed; whoever has more rights than their task requires is downgraded.

Amazon has announced that it removes secondary users who have not signed in for more than twelve months. That is a safety net, not a substitute for your review: someone who signs in now and then slips through.

Most common mistake

Ending a collaboration without removing access. The agency is let go, the last invoice paid, and its access with admin rights stays in place. Months later bids change without anyone on the team having done it, sometimes only because a forgotten tool of the agency keeps running. The cause is always the same: access without an owner.

4

Two-step verification and passkeys

When you sign in, Seller Central asks for a second proof in addition to the password. You set up this two-step verification in your login settings, with a default method and at least one backup method: authenticator app, text message or voice call.

MethodStrengthWeakness
Authenticator appWorks without mobile signal, codes expire within secondsLost with the phone if there is no backup
Text messageSimple, works on any phoneVulnerable if someone gets your number moved to another SIM card
Voice callFine as a backup, even via landlineImpractical for everyday use
PasskeyBound to your device, useless on a fake pageNeeds a second device or a backup method

Since July 2026 Amazon has offered passkeys for all Seller Central accounts and has announced that they will become mandatory for some accounts. A fraudster can talk you out of a code on the phone or capture it on a cloned page, while a passkey only works on the genuine Amazon site. Every secondary user creates their own.

Three settings decide whether the second step really protects you:

  • Backup method on a different device. Default and backup on the same phone are a single point of failure.
  • “Don’t ask again on this browser” only on your own computer. On shared or public devices the option switches off the second step.
  • Protect the mailbox like the account. Whoever takes over your mailbox can have passwords reset. It needs its own two-factor sign-in and a password used nowhere else.
Important

Amazon never asks you for a verification code, a password or your bank details, whether by email, phone or chat. A code you did not request means someone is trying to sign in with your password right now. Change it immediately.

5

Reviewing and revoking third-party apps

Every connected piece of software has its own access to your data, not by password but by authorization, and is forgotten even more easily than a secondary user.

  • Seller Central: on the “Manage Your Apps” page you see and revoke every authorized app. New authorizations are valid for 365 days and are extended there. Treat the renewal as a reason to review, not as a click routine.
  • Advertising console: under Access and Settings there is a separate tab for third-party applications. Only whoever granted an authorization can revoke it. If that person is gone, remove their user; that also ends the app’s access.
  • Amazon customer account: some tools sign in via a personal Amazon login. You find those permissions in your account under apps and services with data access.

Check each app: who authorized it, is that person still on the team, was the app used recently? Revoking does not delete data the provider already has. Request deletion in writing and, for customer data, check the data processing agreement (see AI for analysis and customer service).

6

Recognizing phishing and account takeover

Most takeovers do not start with a technical attack but with a message that looks genuine. The patterns repeat:

BaitTypical lineHow you recognize it
Looming suspension“Your account will be deactivated in 24 hours”No matching notice in account health
Verification“Confirm your identity and bank account”The link does not end in an Amazon domain
Buyer message“Photos of the damage at this link”External link or archive attachment instead of a photo in the messaging system
Call from “support”“Please tell me the code”Amazon never asks for codes or passwords
Outstanding fee“Pay here or face suspension”Fees run through your seller account, never through a payment link

This leads to the working rule: never sign in through a link in a message. Open Seller Central from a bookmark or by typing the address yourself. Genuine notices about your account also appear there under performance notifications and in account health; if the warning is missing there, it is very likely fake. Forward suspicious emails to the address Amazon gives, stop-spoofing@amazon.com, and then delete them. Safe handling of genuine buyer messages is covered in buyer messages.

Once an attacker has access, they leave traces:

  • a changed bank account, the main target of almost every takeover;
  • new users or changed rights in user permissions;
  • a changed email address or phone number on the sign-in, often shortly before the bank change, so that Amazon’s notices no longer reach you;
  • strange offer changes to price, quantity or handling time, or unfamiliar products suddenly offered from your account;
  • codes and sign-in notices you did not trigger yourself.
7

When you suspect something: the first hours

In a takeover, hours count, not days. Work in this order, because each step depends on the previous one:

  1. Secure the mailbox: change the email password and check its two-factor sign-in. Whoever reads your mailbox reads every reset link.
  2. Secure the Amazon sign-in: sign in via the typed address, change the password, remove unknown two-step methods and passkeys.
  3. Remove unknown access: delete unknown users and partners, revoke suspicious app authorizations.
  4. Check the bank account: if it is wrong, contact Seller Support immediately and inform your bank at the same time.
  5. Document: screenshots of the changes, times, the suspicious email. Amazon, your bank and possibly the police will need them.
  6. Check data protection: if outsiders could see customer data, the GDPR may require notifying the supervisory authority, usually within 72 hours. When in doubt, ask a data protection consultant or a specialist lawyer.
Example

Sunday, 9:40 p.m.: after a “verification required” email, the AURELO seller enters his password and text message code on a deceptively real page. At 9:55 p.m. he notices the address did not end in amazon.de. He changes his mailbox password first, then his Amazon password, switches two-step verification to the app and finds a new user, created at 9:47 p.m. He removes it; the bank account is unchanged. Monday morning he reports the incident to Seller Support with times and screenshots. Fifteen minutes were enough because the steps were written on an emergency sheet.

Tip

Print the emergency sheet: the six steps, the Seller Central address, your bank’s phone number, where the backup codes are kept. In an emergency your computer may not be trustworthy.

Security checklist
  • Every person has their own sign-in; nobody shares credentials.
  • Rights follow least privilege; admin only for you and one deputy.
  • Access list kept for Seller Central, the advertising console and Brand Registry.
  • Backup method on a second device, passkey created.
  • Mailbox with its own two-factor sign-in and a password used nowhere else.
  • Users and apps reviewed quarterly, emergency sheet printed.
8

Expert insight: a takeover is a race against the payout date

Attackers usually want your balance, not your account. The damage therefore depends less on the attacker’s skill than on two quantities: how much money builds up between two payouts and how long it takes you to notice the change.

Run the numbers for the AURELO set: 19 sales a day at €24.99 is about €475 of revenue. After fees and advertising, roughly €300 a day remains as payout (assumption). Amazon usually pays out about every 14 days. Shortly before the payout date there is therefore about €4,200 in the seller account, and that is exactly what a bank change is aimed at.

Time until discoveryWhat can happen in that timePossible risk
under 1 dayBank change spotted before a payout runslow
3 to 7 daysOne payout can go to the attacker’s accountup to one cycle’s balance, here about €4,200
over 14 daysSeveral payouts, plus changes to offersa multiple of that, plus damage to the account

Three levers follow, and none requires specialist technical knowledge:

  • Shorten detection time. Notices about changed sign-in or bank details must land in a mailbox that is read daily and that the attacker does not control. A second recipient, such as a dedicated security mailbox only for account notices, raises the chance that someone looks in time.
  • Secure the chain at the first link. An attack almost always runs the same way: mailbox, sign-in, contact details, bank. A strong Amazon password helps little if the reset link lands in a weakly protected mailbox.
  • Put the check into the rhythm. A look at the deposit method and the user list belongs in the weekly routine. Two minutes a week against a cycle balance of €4,200: insurance does not get cheaper.

One more point many overlook: after an unauthorized change has been reported, Amazon often reviews the account further and may temporarily hold payouts or reset payment methods. That is intended. Plan liquidity for it, as with the emergency folder from the account health lesson.

✎ Practice

Your turn: 2 exercises

Solve them to unlock the quiz. Up to 30 points each when you get it right first time without a hint.

1
Spot the mistakes

Find the phishing signs in this email

This email lands on Sunday evening in the inbox of the seller behind the AURELO spice grinder set. Click every part that points to phishing.

From: Amazon Seller Central (service@amazon-seller-verify.com)Subject: Your seller account will be deactivated in 24 hoursHello,during a routine review of your account we noticed some inconsistencies.Please confirm your bank account and tell us the code we will send you by text message.Use this link to do so: sellercentral-amazon.de.account-check.net/loginYou can see the current state of your account at any time in account health in Seller Central.Thank you for your cooperation.Attachment: Account_check_form.zipYour Amazon Seller Central team

Tap every part that contains a mistake (5 in total).
2
Sort it

Who gets which right?

The AURELO seller works with an employed customer service assistant, a PPC freelancer and an accounting firm. Assign each task to whoever may carry it out under the principle of least privilege.

Answer buyer messages
Change bids and budgets
Pull settlement reports
Change the bank account
Process returns
Download search term reports
Grant rights to new users
View tax reports

Check yourself

6 quick questions, one at a time, with instant feedback. With a free account your progress is saved.

An accounting firm needs to pull your settlement reports. Which access fits?
External providers go through the roles Amazon has vetted them for and that you confirm. Secondary users are meant for your own employees, and Amazon does not support shared sign-ins.
Why is it risky to keep the default and backup methods of two-step verification on the same phone?
The backup method is meant to work when the default fails. If both sit on one device, a lost or broken phone locks you out, and only the lengthy account recovery remains.
You receive a verification code by text message without signing in. What does it most likely mean?
Codes are only sent during a sign-in with the correct password. An unrequested code means the password is known and only the second step stopped the attacker. Change it immediately.
A dismissed agency authorized an app in the advertising console and does not respond. How do you end the access?
Only whoever authorized can revoke. If that person is unreachable, remove their user; the app then loses access too. Additionally request deletion of any data already stored.
You entered your credentials on a fake page. Where do you start?
As long as the attacker controls your mailbox, they intercept every reset link. Only then do you secure the Amazon sign-in, remove unknown access and check the bank account.
During an incident, outsiders could see customer data. What do you check besides securing the account?
A personal data breach can be notifiable under the GDPR, usually within 72 hours. Whether that applies is something to clarify with a data protection consultant or a specialist lawyer when in doubt.

Frequently asked

May my assistant use my sign-in if I trust them?

No. Amazon does not support shared sign-ins, and with shared access you can neither trace who changed what nor block a single access. If the assistant is your employee, invite them as a secondary user with their own sign-in. If they work externally, access runs through approval as an authorized partner or through work done outside the account.

What do I do if I lose the phone with the authenticator app?

Sign in with the backup method, remove the lost device from your login settings and set up the app on the new device. If you no longer have a working backup method, the only route is account recovery through Amazon with proof of identity, and that can take time. That is exactly why the backup method belongs on a second device.

How do I tell whether an email really comes from Amazon?

Not by the sender alone, because that can be forged. Open Seller Central from a bookmark and check whether the notice also appears under performance notifications or in account health. If it is missing there, asks for codes, passwords or bank details, or puts you under time pressure, treat it as phishing and forward it to stop-spoofing@amazon.com.

← Previous lessonPackaging that cuts costs and returns: FBA rules, frustration-free packaging, eco badges Next lesson →Handing off tasks: using freelancers and agencies the right way
Enes Kurt
Founder of Listimo

Everything in this academy comes from more than ten years of hands-on work with Amazon listings, the same playbook behind Listimo: the tool that finds what holds an Amazon listing back and fixes it.