For AI service providers · Capability
How do client AI workspaces keep service delivery separate?
Use one Team workspace per client, then verify its members, agents, files and connected accounts before running client work. Agentic Workers supports this workspace model and a workspace switcher. Teams require the eligible plan; separate workspace names do not by themselves prove every external tool or shared resource is correctly scoped.
By Agentic Workers Team · Published · Updated
Set the boundary first
Create the Team before adding client tools or files. Choose the account owner and invite only the people who need access. Confirm the active workspace after switching; new configuration belongs to that selected context.
Check the agent’s accounts
A workspace can contain several agents. For client integration links, the selected Super Agent uses Agent only integration mode. Shared organization accounts are a separate configuration choice, so review both account mode and the selected client identity.
Prove the exit
Remove a test member and verify access is denied. Revoke an unused portal link and test it again. Keep separate records of disconnected accounts, retained files and stopped schedules.
Example provider workflow. Adapt it to the client’s agreed scope.
- 01
Create
Name the Team for one client and confirm the owner.
- 02
Connect
Attach only that client’s files and authorized accounts.
- 03
Verify
Test with two fictional clients and a removed test member.
Fit and limitations
- Good fit
- Providers with separate clients and an operator responsible for access checks.
- Poor fit
- A single shared agent holding several clients’ sensitive files, or buyers requiring unverified infrastructure isolation.
- Known limits
- Creating Team workspaces requires the owner’s Ultra plan. Workspaces are an application boundary, not a promise of dedicated databases or a compliance certification. Review records within each workspace; do not assume a unified cross-client dashboard, consolidated client billing, or full-workspace cloning.
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 |
|---|---|---|
| Team workspace setupProduct documentation | Teams organize agents and connected tools by workspace. Verify membership and the active workspace before setup. | |
| 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. | |
| Read an agent run recordProduct documentation | Inspect available tool calls and execution details within the relevant workspace. A completed run is not proof of an accepted result. |
Questions providers ask
What should we test before using client data?
Name the Team for one client and confirm the owner. Attach only that client’s files and authorized accounts.
What should the provider verify after a run?
Test with two fictional clients and a removed test member.
What is the main limitation?
Creating Team workspaces requires the owner’s Ultra plan. Workspaces are an application boundary, not a promise of dedicated databases or a compliance certification. Review records within each workspace; do not assume a unified cross-client dashboard, consolidated client billing, or full-workspace cloning.
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