The short answer
An Amazon agency needs scoped access to Seller Central or Vendor Central, the Amazon Ads console and sometimes Brand Registry, never the brand's own login. As of November 2026, Amazon's developer documentation has service providers request Seller Central access through Solution Provider Portal, the seller reviews and can narrow the roles, and the authorization lasts 365 days. Ads access comes as an admin, editor, viewer or custom role. Brand Registry's Rights Owner and Administrator roles stay with brand employees.
An Amazon agency needs access to four places to do its job: Seller Central (or Vendor Central), the Amazon Ads console, Brand Registry, and any software connected to the account through the Selling Partner API. It never needs the brand's own login. Each of those four has its own way to grant scoped, revocable access, and the brand should be the one holding the keys to all of them.
This matters most on the day a relationship starts and the day it ends. A brand that hands over a password, or lets an agency open accounts in the agency's name, finds out at the end that getting its own campaigns, reports and listings back is a negotiation. A brand that grants access role by role just switches it off.
Why shouldn't an Amazon agency use the brand's login?
An Amazon agency shouldn't use the brand's login because Amazon's tools are built to give outside firms their own scoped access, and a shared login removes every control the brand has. Amazon announced in its Seller Forums that, starting as early as March 28, 2024, sellers would have to verify their identity at Seller Central sign-in with a mobile number or authenticator app. A shared login means sharing that second factor too, so nobody can say afterward who changed a price or deleted a campaign.
Amazon's own guidance is blunt about outside firms. In a Seller Forums post on account user permissions, Amazon wrote: "Don't add external third-party service providers or developers as users." The same post tells sellers to "grant the minimum permissions required for them to do their job" and to review those permissions regularly.
How does a brand give an agency Seller Central access?
A brand gives an agency Seller Central access by authorizing it as a service provider, not by inviting its staff as users. As of November 2026, Amazon's Selling Partner API documentation describes the flow: the agency registers in Solution Provider Portal, Amazon's portal for outside developers and service providers, and is approved for the Seller Central roles its service needs. It then sends the seller an authorization link, or the seller finds it in the Service Provider Network.
The seller stays in control of the scope. Amazon's documentation says the seller "sees the roles that you've been approved for," can adjust individual roles or restrict access before confirming, and can use a country or region filter to limit access by marketplace. Amazon states that "the authorization is good for 365 days." After that, the agency hands out access to its own staff inside Solution Provider Portal, where Amazon describes View, View & Edit and Admin permission levels.
Two details are worth knowing before you click Confirm:
- Personal data is a separate, harder ask. Amazon's service provider registration guide says requests for restricted roles that touch personally identifiable information "undergo additional review," and that access is granted on a need-to-know basis. Most agency work, from catalog to inventory to ads, doesn't need buyer addresses.
- Ask what each role is for. If an agency asks for Admin on everything, ask which task needs it. In our experience, user management and the bank account settings are the two that almost never do.
On Vendor Central accounts we apply the same rules: named access for each person, no shared logins, and the primary account kept by the brand.
What Amazon Ads console access does an agency need?
An agency running Amazon Ads usually needs editor access to the brand's advertiser account. Amazon Ads says its advertiser account supports "standardized roles (admin, editor, viewer)" across sponsored ads and Amazon DSP, and "custom application level (e.g., reporting only) permissions." Since April 2021, admins have been able to give narrower access, such as billing access for a finance team or Stores builder access for a creative agency.
Agencies with several clients typically work from a manager account, Amazon Ads' tool for linking many advertiser accounts in one place. Amazon's help page on manager accounts, updated February 24, 2026, lets an admin invite users either to the whole manager account, which gives them "access to all accounts within the manager account," or to selected accounts only. That's convenient for the agency. It also means one invite on their side can reach your account, so the link itself is the thing to control.
The advertiser account guide also says billing can sit with either the manager account or the advertiser. Sell Through's view is that billing should sit with the brand. When the invoice goes to the agency, the brand loses a clean record of what it spent, and leaving the agency gets harder than it should be.
Which Brand Registry roles should an agency get?
An agency should never hold the Rights Owner or Administrator role in Brand Registry. Whether it gets the Registered Agent role is the brand's call, and Amazon's own guidance pulls both ways. Amazon's guide to Brand Registry roles lists three protection roles (Rights Owner, Administrator and Registered Agent) and two selling roles (Brand Representative and Reseller):
| Amazon describes for the brand itself | Amazon describes for outside parties |
|---|---|
| Rights Owner: protection benefits such as Report a Violation, assigned to the trademark owner | Registered Agent: for third parties the trademark owner authorizes to report suspected IP violations |
| Administrator: can assign and update protection and selling roles for the brand | Not described for outside parties. Amazon recommends more than one Administrator |
| Brand Representative: for sellers directly employed by the brand, with full Brand Analytics | Reseller: for authorized third-party sellers, with limited benefits and no Brand Analytics |
Here's the tension. Amazon says Registered Agent is for third parties, yet the same guide also says: "Only assign protection roles to employee accounts, or other accounts internal to the brand." Sell Through's read is to keep Rights Owner and every Administrator seat with named brand employees, and to grant Registered Agent to an agency only when it files reports for you under a written authorization, then remove it when that work stops. An agency running your own selling account doesn't need the Reseller role, which is built for outside sellers.
What about apps and tools connected to the account?
Every app connected to Seller Central or Vendor Central through the Selling Partner API is another door into the account. Public apps a seller has authorized show up in Manage Your Apps. Amazon's documentation says a seller must reauthorize a public app "every 365 days, or anytime you add a role to your application." When a seller revokes an authorization, the app is disabled. The path is Apps and Services, then Manage Your Apps, then Disable authorization. Vendors choose Menu, then Integration, then API Integration, then Manage Apps.
Agencies often bring their own software for bids, reports or inventory. That's normal. Ask for the list of apps they'll connect, and check it against Manage Your Apps on the day they start and the day they leave.
How do you set up and remove agency access?
Set up agency access the same way every time, and write down what you granted so you can undo it. This is the order we work in when we start with a brand:
- 01
Keep the owner seats
The primary Seller Central or Vendor Central account, the Ads admin seat and the Brand Registry Rights Owner and Administrator roles all stay with named brand employees.
- 02
Authorize, don't invite
Approve the agency through Amazon's service provider authorization, review each role, and limit it to the marketplaces they'll run.
- 03
Scope the Ads access
Give editor access to the advertiser account, or link their manager account. Keep billing on the brand's side.
- 04
Log it and review it
Record every role and connected app with a date. Review the list every quarter, and the day the work ends, disable all of it.
When you part ways, the checklist is short: remove the agency's access to Seller Central or Vendor Central, disable any app it connected in Manage Your Apps, remove its manager account link or users in the Ads console, and remove any Registered Agent role in Brand Registry. Then confirm that your campaigns, reports and listings are all still there. If the agency never owned any of the accounts, they should be.
For what an agency does once it's inside the account, see what an Amazon agency actually does. For how we run the account side, including resellers and Brand Registry, see our channel control and brand protection service and our Amazon page.
Common questions
Should I give my Amazon agency my Seller Central login?
No. Amazon tells sellers not to add outside service providers or developers as users, and a shared login gives up even the controls a user account has. As of November 2026, Amazon's developer documentation describes service providers requesting access through Solution Provider Portal, with the seller reviewing the roles and able to adjust or restrict them before confirming.
How long does an Amazon service provider authorization last?
Amazon's Selling Partner API documentation says a seller's authorization of a service provider "is good for 365 days." Public apps connected through Manage Your Apps also have to be reauthorized every 365 days, or whenever the app adds a role.
What Amazon Ads console access does an agency need?
Usually editor access to the advertiser account, granted directly or by linking the agency's manager account. Amazon Ads offers standardized admin, editor and viewer roles across sponsored ads and Amazon DSP, plus custom application-level permissions such as reporting only. Keep at least one admin seat inside the brand.
Can an Amazon agency file Brand Registry infringement reports for my brand?
It can, through the Registered Agent role, which Amazon describes as being for third parties with the trademark owner's authorization to report suspected IP violations. The same Amazon guide also advises assigning protection roles, a group that includes Registered Agent, only to accounts internal to the brand, so grant it deliberately and keep Rights Owner and Administrator in-house.
Sources
Everything above is drawn from these documents. Where a figure is ours, the text says so. Spotted an error? Our corrections policy says how we fix it.
- 01Learn How Sellers Authorize Service Providers
Amazon Selling Partner API documentation
- 02User Permissions for Service Providers
Amazon Selling Partner API documentation
- 03Register as a Service Provider (Setup and Migration)
Amazon Selling Partner API documentation
- 04Reauthorize Applications
Amazon Selling Partner API documentation
- 05Revoke Authorizations
Amazon Selling Partner API documentation
- 06Seller Account User Permissions
Amazon Seller Forums
- 07Two-factor authentication will be required for Seller Central sign in
Amazon Seller Forums (News_Amazon)
- 08
- 09Advertiser account
Amazon Ads
- 10Invite users to your Manager account (MA)
Amazon Ads Support Center
- 11Custom access controls
Amazon Ads