Managing multi-account, agency and partner workflows

Work across clients and partners without collapsing their ownership or authority. The planned outcome is an explicit delegated workflow, not a shared master key.

Select the account intentionally

A person may administer more than one account. Applications belong to one account, and each request must retain its application/account attribution. Names or matching email addresses do not merge records or balances.

Workspace collaboration is not automatically cross-account delegation.

Define an agency handoff

Specify the client, data/resource scope, permitted actions, duration and who can approve changes. A reusable agency playbook can create planning artifacts, but execution still needs the client's applicable permissions, consent and funding.

For example, an agency can review a client's draft Store without receiving authority to register its domain or charge its payment method.

Separate partner roles

Operator onboarding, offers, device evidence, proof review, earnings and affiliate programs require their own eligible roles and agreements. General customer status should not expose private partner verification or finance administration.

Revoke and review

Delegation must be reviewable and revocable without moving data ownership. A permission change should affect later requests even if an old browser view or key remains cached.

Availability

Business APIs are planned. This guide does not create a reseller program, blanket partner entitlement, cross-account wallet or live integration.