Skip to content

Approving a connector action

An assistant connected to your store can read a great deal and change comparatively little on its own. When it proposes something it is not allowed to do unattended, it does not do it and does not fail silently — it produces a confirmation link, and a person decides.

That link opens the handoff page.

A connector that could do everything it was asked would be a connector whose worst day is your worst day. The confirmation step is not friction added for its own sake: it is the boundary between what an assistant may do because you set it up, and what it may do only because you looked at this particular change and said yes.

The page shows you four things before you answer:

Shown What it tells you
Capability Which named ability the assistant is asking to use.
Requested by Who or what proposed it.
Permission required The permission an account must hold to approve it.
What would change A preview of the actual change, not a description of the category.

Read the preview. The capability name tells you the kind of change; only the preview tells you this change.

Saying yes does not grant the assistant the capability from now on. It authorizes this one proposal, one time — the page says so, and the state moves to “already carried out” once it has been used.

There is no way to approve a class of future actions from this page. If an assistant needs to do something routinely without asking, that is a permissions decision made in the admin, not something you can widen from a confirmation link.

The four states, and what to do about each

Section titled “The four states, and what to do about each”
  • Waiting for your answer — the only state in which anything can be decided.
  • Approved — you said yes; the assistant may carry it out once.
  • Already carried out — it has been used. Nothing further happens from this link.
  • Expired — time ran out. The proposal is dead; the assistant must propose again.

Two refusals are worth recognizing rather than retrying:

“You cannot answer this one.” The action needs a permission your account does not hold. This is not a bug and re-opening the link will not change it — a colleague who can perform that action in the admin has to open the same link.

“Nothing to confirm.” The link does not name a pending action in this store. It was answered already, it expired, or it belongs to a different store. A handoff link is scoped to one store; opening it while signed in to another is a common and harmless way to reach this message.

The address contains a one-time token. Anyone who can open it and holds the required permission can answer it.

🔴 Do not forward a handoff link into a shared channel to ask whether it looks right. Send the question, not the link. If the right person needs to approve it, they can be given the link directly — and if it has already leaked somewhere public, let it expire rather than approving it.

  • It does not describe connecting an assistant in the first place. That is an apps and permissions decision made in the admin.
  • It does not list which capabilities require confirmation. That set belongs to the connector and its granted scopes, and a list written here would go false the first time either changed.
  • It does not undo anything. Declining stops an action that has not happened. An action already carried out is undone the same way any other change is — in the screen that owns it.