selling-partner-invite-secondary-users

Overview

Helps the primary user of a Seller Central account bring their team onto the Selling Partner plugin. After the connector is connected, it confirms the person is the account owner or administrator, asks whom they want to invite, and guides them through granting AI-agent access on the Manage Agents page in Seller Central, the control that lets a secondary user authorize the plugin. When it runs in Amazon Quick there is a second grant: inviting that user as a collaborator on the Quick account. It is advisory and read-only: there is no operation that flips agent access, so the skill guides the human through the UI and never performs the grant itself.

Workflow

<Definition - Primary User vs Secondary User> The primary user is the account owner or an administrator of the Seller Central account; only they can grant AI-agent access on the Manage Agents page. A secondary user is any other user on the account, who cannot grant themselves access and must ask an administrator. Confirming which one you are talking to is the gate before any grant steps. </Definition - Primary User vs Secondary User>

<Definition - The Two Grants on Quick> On Amazon Quick a secondary user needs both grants to use the plugin: the Seller Central Manage Agents grant (the Amazon-side authorization that lets them authorize the plugin), and collaborator access to the primary user's Quick account (because the plugin and its skills are used within a Quick account). Manage Agents alone does not give Quick access, and Quick collaboration alone does not authorize the plugin against Seller Central. In a non-Quick assistant only the Manage Agents grant applies. </Definition - The Two Grants on Quick>

<Workflow - Invite Secondary Users description="Guide the primary user through granting a secondary user AI-agent access: confirm the connector and admin role, give the Manage Agents steps, add the Quick collaborator step when on Quick, and summarize what is left to the user." tools=[] triggers=["invite users", "add a secondary user", "manage agents", "grant agent access", "let my team use the plugin", "onboard my team", "give access to another user"]

1. [Agent] Confirm the built-in Amazon Selling Partner connector is connected, per the README pre-requisites. This skill assumes the plugin is already connected. Validate: The connector is connected and authenticated. If fails: Tell the primary user to connect and authenticate the Amazon Selling Partner connector first (via onboarding or the connect flow), and stop rather than giving grant steps for an unconnected plugin.

2. [Ask user] Confirm the role. Ask directly: are you the primary user (account owner or administrator) of this Seller Central account? Validate: The person states whether they are the account owner/administrator. If fails (no or unsure): Explain that only an administrator can grant AI-agent access on Manage Agents, tell them to ask their account administrator to run this, and stop (Rule 2). Do not give the grant steps.

3. [Ask user] Offer to invite, but do not block on the answer. Ask whom they want to invite (person or role, and the email or Seller Central user it maps to so they can find the right row), and go straight into the Manage Agents steps in the same turn, using a neutral placeholder like "the user you want to add" if no specific name is given yet. Never invent a user or email (Rule 4). Validate: The grant steps are presented in this turn, with a real provided identity or a clear placeholder. If fails: If the person supplies a partial identity, use what they gave and continue; do not stall waiting for details.

4. [Agent] Guide the Manage Agents grant (Seller Central), concretely and now (Rule 5). For each user: sign in to Seller Central as the owner/administrator, go to the Manage Agents page, find the user, and enable their AI-agent access (disable it there to revoke later). State that this grant is what lets the secondary user authorize the plugin, and that they must still connect the plugin and sign in with their own Amazon selling account afterward (Rule 8). See references/manage-agents-guide.md. Validate: The concrete Manage Agents steps and the "what the user must still do" note are given. If fails: If any step is unclear, restate it plainly from the reference rather than deferring.

5. [Decide] Is the skill running in Amazon Quick? (Rule 3, <Definition - The Two Grants on Quick>)

   • Running in Quick: include the collaborator step (step 6).
   • Running in a non-Quick assistant: skip the collaborator step and say no Quick collaborator step is needed here.
   • Unsure: ask whether they are using the plugin in Amazon Quick or another assistant, then branch. Validate: A surface determination is made (Quick, non-Quick, or asked). If fails: Ask the surface question rather than assuming.

6. [Agent] Quick only: guide the collaborator invite. Invite the same user (same person/email) as a collaborator on the Quick account, and frame it clearly as two grants both required on Quick: Manage Agents access in Seller Central, and collaborator access in Quick. See references/quick-collaborator.md. Validate: The collaborator step is given and framed as required alongside Manage Agents. If fails: If Quick menu labels have changed, state the requirement (the user must be a Quick collaborator in addition to the Manage Agents grant) even if the exact navigation differs.

7. [Agent] Summarize per user, in plain language: Manage Agents AI-agent access (granted or pending), Quick collaborator (granted or not applicable off Quick), and what the secondary user must still do themselves (connect the plugin and sign in with their own Amazon selling account, and on Quick accept the collaborator invite). Offer to repeat for the next user. Validate: A short per-user recap with the remaining user-side actions is produced. If fails: If any grant's state is unknown, mark it pending rather than asserting it is done.

</Workflow - Invite Secondary Users>

Reference files:

• references/manage-agents-guide.md: the exact Manage Agents grant steps in Seller Central, who can do it, what the grant does and does not do, and good practice.
• references/quick-collaborator.md: the Quick-only second grant, inviting the user as a collaborator on your Quick account, and why both grants are required on Quick.