For AI service providers · Capability
How do you set up AI agents with customer-owned accounts?
Separate account ownership from the provider’s operating role. The client should control the source accounts it needs to retain; the provider configures only the access needed for the service. Agentic Workers supports client tool authorization links. Confirm workspace ownership, billing and the exit procedure before starting work.
By Agentic Workers Team · Published · Updated
Record ownership before setup
Write down the owner of the workspace, each source app, runtime and billing account. A client-owned tool connection does not automatically make the client the owner of the agent environment or platform subscription. Agree on those separately.
Let the account owner authorize access
The client can use a scoped portal invitation to connect a supported app to the selected agent. Confirm the intended account with a read-only check. Avoid moving the client’s credentials into the provider’s personal accounts to make a demo easier.
Verify the exit together
Stop recurring work, collect agreed output, revoke active invitations and disconnect accounts. Remove operator access where appropriate and confirm the client can still access its original source accounts. Contractual data ownership and retention are separate from these UI actions.
Example provider workflow. Adapt it to the client’s agreed scope.
- 01
Assign
Client and provider record account, runtime and billing owners.
- 02
Authorize
Client connects the supported tools required by the service.
- 03
Rehearse
Use safe data to verify access removal and the agreed handoff.
Fit and limitations
- Good fit
- Providers and clients who want explicit account ownership and a practical exit plan.
- Poor fit
- A promise of automatic transfer of all accounts, subscriptions, files and runtime state.
- Known limits
- No automatic legal ownership transfer, certified deletion or complete one-click offboarding is claimed. Verify retention and exports for the client’s specific requirements.
Sources and evidence
Documentation establishes the scope of a claim. It does not replace an acceptance test in your client’s environment.
| Source | What it supports | Checked |
|---|---|---|
| Customer portal operating notesProduct documentation | Upload and app-connection invitations are scoped to a selected agent. Revoking an invitation is separate from disconnecting an account. | |
| Team workspace setupProduct documentation | Teams organize agents and connected tools by workspace. Verify membership and the active workspace before setup. | |
| Current plans and billingProduct documentation | Confirm current plan eligibility and separate third-party usage. No numeric pricing comparison is made here. |
Questions providers ask
What should we test before using client data?
Client and provider record account, runtime and billing owners. Client connects the supported tools required by the service.
What should the provider verify after a run?
Use safe data to verify access removal and the agreed handoff.
What is the main limitation?
No automatic legal ownership transfer, certified deletion or complete one-click offboarding is claimed. Verify retention and exports for the client’s specific requirements.
Set up one client service
Set up the client workspace, connect its tools and review the first deliverable. Use a tested delivery path, such as Telegram, so the client can receive work in chat. Track operating costs and review effort before pricing a recurring service.
Sign up now