Permissions, scopes and account access

Who can approve a connection

Only workspace owners can authorize a new AI connection. Operators and viewers can use the dashboard but cannot connect an AI tool. Agentic Sellar re-checks workspace membership, the workspace itself, grant expiry and revocation on every request, so removing someone from a workspace stops access through their connections.

Account grants

When an AI tool connects, the owner chooses which connected Amazon accounts it may use, or allows all accounts in the workspace, which automatically includes accounts connected later. Seller Central accounts need a seller: scope and Amazon Ads accounts need an ads: scope. A grant is bound to the exact account, marketplace and Amazon identifier it was approved for; reconnecting an account under a different Amazon identity does not carry old grants across.

Scopes

New connections are asked for the three read scopes. The consent screen lists all six with the AI tool’s request ticked, and the owner decides which ones the connection gets.

Read-only by default

When an AI tool first connects, Agentic Sellar’s 401 challenge includes scope="workspace:read ads:read seller:read", and its OAuth metadata advertises only those scopes. A client that follows the MCP authorization specification therefore asks for read access, and write access is never granted without a workspace owner’s approval.

• On the consent screen the owner can untick any requested scope, or tick a scope the AI tool did not ask for. Leaving every write scope unticked approves read-only access.
• If a connection calls a tool its scopes do not cover, Agentic Sellar answers with HTTP 403 and error="insufficient_scope", naming the scopes the connection already holds plus the one the tool needs. Clients that support step-up authorization, such as Claude, send you back to the consent screen to approve it. Others show an error or ask you to reconnect.
• Agentic Sellar remembers the refused scope for an hour. If you reconnect that AI tool in that time, its consent screen ticks the scope, marked “Needed by a tool call”, along with the access the connection already has, even when the AI tool repeats its first request. Nothing is granted until you approve it. After the hour, tick the scope yourself.
• Approving more access creates a new grant with the combined scopes. The earlier one stays on the Agent access page until it expires or you revoke it.
• Some AI clients treat a grant narrower than their request as a failed connection. If a connection fails after you untick a requested scope, connect again and keep that scope, then limit the connection by account instead.

How writes are confirmed

• A write tool only runs if the grant includes the matching write scope.
• Every write call must include confirm: true. Calls without it are rejected before Amazon is contacted.
• Write tools are published with MCP annotations readOnlyHint: false and destructiveHint: true, which clients such as Claude and ChatGPT use to ask for your approval.
• The curated campaign-state tool can enable or pause a campaign but never archive one, because archiving cannot be undone in Amazon Ads.
• General Amazon Ads and Selling Partner API write tools follow the permissions of the connected Amazon application and are subject to the same scope and confirmation rules.

What your plan allows

Live reads and writes are available on every paid plan. Operations that read retained history need a Data plan; on Access they return retained_data_not_included and suggest a live alternative. Plans also set monthly work units and how many requests can run at once. See the plan comparison.

Expiry and revocation

• Access tokens last 60 minutes. Clients refresh them automatically within the grant.
• A grant lasts at most 30 days; after that the AI tool must be approved again.
• You can revoke the connections you authorized immediately from Settings → Agent access. Revoking with either the access or refresh token through the OAuth revocation endpoint also ends the grant.