Key takeaways
- Never share your Seller Central password.
- Grant the least privilege each role needs.
- Review users on a schedule.
- Revoke access immediately when work ends.
Why not share a password
Shared credentials remove accountability, make it hard to remove one person's access and can conflict with security settings such as two-step verification. Permissions assigned to individual users avoid these problems.
Each person should have their own login and only the access their role requires.
How permissions are structured
Seller Central allows the primary account owner to invite users and set permission levels by area, such as inventory, orders, advertising, reports, payments and account settings. Options are typically no access, view only or edit.
The exact names and structure can change, so check the current user permissions page when you set this up.
Designing least-privilege access
Start from the tasks a person will perform and grant only what those require. A reporting analyst may need view access to reports but no payment access. A listings specialist may need catalog edit rights but not advertising or payments.
Document the role and the reason for each permission so reviews are quick.
- Reporting roles: view access to reports and performance
- Listing roles: edit catalog and inventory content
- Operations roles: orders, shipping and returns
- Finance roles: payments and settlement, tightly limited
Onboarding an agency
Send invitations to individual agency staff rather than a shared mailbox where possible. Agree the permission list in writing. Ask which team members need access and review that list at set intervals.
Reviewing and revoking access
Review users at least quarterly. Remove people who have left or changed roles, and re-check after any staffing change. When an engagement ends, revoke access the same day and confirm in writing.
Keep a log of who was granted what and when.
A worked example of role design
Suppose you work with an agency for listings and advertising, a freelancer for images and an accountant for settlement reports. The agency needs catalog and advertising access but not payments. The freelancer may need only the ability to upload images through the relevant listing tools. The accountant needs read access to payment reports and nothing else.
Writing the roles down in this way makes it simple to review later, and it shows quickly when someone has more access than their job requires.
Common mistakes
The most frequent mistake is granting broad access for convenience and never narrowing it. Another is leaving former staff or contractors in the user list for months. A third is relying on a single owner login with no documented recovery path.
Build a quarterly review into your calendar, and treat any change in staffing as a trigger for an immediate access check.
Your next three steps
Tighten access this week with three small actions.
- Export your current user list and mark anyone who no longer needs access.
- Write the minimum permission set for each role and compare it with reality.
- Calendar a quarterly review and a same-day removal rule for leavers.
Frequently asked questions
Can an agency see my payments?
Only if you grant that permission. Many roles do not need it, so you can withhold it.
Do users need two-step verification?
Amazon requires or strongly encourages it for accounts. Follow current account security requirements.
This guide is general information. Amazon's fees, policies and program rules change and vary by marketplace, so confirm current details in Seller Central and, for tax or legal questions, with a qualified adviser.