What needs a person
The few acts an agent hands back to a human, why, and the tool that prepares each one.
An agent can run nearly everything. A few acts stay with a person on purpose: they need someone's own login elsewhere, they spend the agency's money on a plan, or they cannot be undone. For each, a tool prepares the handoff so the person has one thing to click.
Act | Why a person | What the agent does |
|---|---|---|
Approve the agent in the first place | access is granted by someone accountable for the agency | ask them to add the MCP connector and sign in, or to create a key under Settings → API keys |
Grant access to Search Console or GA4 | only the property's owner can add a user |
|
Make a Yandex Webmaster token | it is minted in the site owner's Yandex account |
|
Connect by sign-in instead (and Business Profile, which has no other route) | it needs a sign-in to the client's Google or Yandex account |
|
Change the plan | it charges the agency |
|
Make someone an owner | owners can do anything, including close the agency | ask an owner to do it in Settings → Team |
Sign up a new teammate | an account is a person's own | ask them to sign up; then |
Close the agency or export all its data | irreversible, or the whole account at once | ask an owner to use Settings → Ending this account or Data export |
When a tool is refused for a permission the credential lacks, the refusal names the permission. Tell your person which act needs it rather than asking for a broader credential than the job requires.