Claude at work: why an organization account and not an employee's personal account
By Asaf Yoshpe, CEO, CloudX
Published: Last tested:
The short answer
An employee who uses Claude for work from a personal account keeps the organization's knowledge in an account the organization does not control. That is true whether the employee pays for Pro, Max or Ultra out of pocket or the company reimburses the cost.
An organization account (Team or Enterprise) changes three things: content is not used to train models by default, the accounts belong to the organization rather than the employee, and an admin decides who connects to which systems.
Most of the discussion online focuses on training. In our experience with clients, the bigger problem is ownership: what happens to the chats, projects and system connections on the day the employee leaves.
What actually differs
A personal account means Free, Pro, Max or Ultra. Even the paid plans are governed by the consumer terms. Team and Enterprise are governed by the commercial terms.
| Topic | Personal account (Free, Pro, Max, Ultra) | Team | Enterprise |
|---|---|---|---|
| Model training on your content | On, unless the employee turns it off in settings | No, by default | No, by default |
| Who controls the privacy setting | Each employee for themselves | The organization | The organization |
| Who owns the account | The employee | The organization | The organization |
| Central billing and spend control | No | Yes | Yes |
| SSO sign-in | No | Yes | Yes |
| Domain verification and blocking new personal accounts on it | No | Yes | Yes |
| Admin-managed connectors | No | Yes | Yes |
| Domain capture (moving existing personal accounts in) and SCIM | No | No | Yes |
| Audit logs | No | No | Yes |
| Custom data retention period | No | No | Yes |
Source: Claude plans page. Current prices are listed there. Team is for organizations of 2 to 150 seats, and Enterprise starts at 20 seats.
Four risks of working from a personal account
1. The knowledge leaves with the employee
Chats, projects, uploaded files and instructions built over months sit in an account registered to the employee's personal email. On the day they leave, the organization has no way to close access, hand the material to a replacement, or even know what is there.
This is not a malicious-employee scenario. It happens with every ordinary departure.
2. The privacy setting depends on each employee
Since October 2025, on personal accounts (Free, Pro, Max and Ultra), chats and coding sessions are used to train models when the setting is on, including Claude Code used from those accounts. When it is on, data is retained for up to five years. When it is off, the retention period is 30 days (Anthropic's announcement, Claude Code data usage).
The setting can be turned off, but the organization cannot enforce it or check it. An organization with 20 employees on personal accounts relies on 20 individual decisions. If you have committed in a contract that a client's data will not be used for training, you have no way to prove you kept that commitment.
3. No control over system connections
Claude is no longer just a chat window. It connects to email, Drive, Slack, Salesforce and the browser. On a personal account the employee decides alone what to connect, and no one in the organization sees it.
On an organization account an admin decides which connectors are allowed. That is the difference between a managed work tool and shadow IT with access to core systems.
4. Knowledge stays with one person
On a personal account each employee builds their own projects, instructions and Skills. The colleague next to them starts from scratch. On an organization account projects and tools are shared with the team, and what one employee improves serves everyone.
What an organization account does not solve
An organization account is necessary, not sufficient. Four things remain your responsibility:
- Policy. Even on an organization account an employee can paste client data that should not be there. Define in writing which data may be uploaded and which environments may be connected.
- Team's limits. Team has no audit logs, no SCIM and no control over the data retention period. An organization with regulatory or audit requirements should look at Enterprise.
- "Not used for training" is not "not stored". The data is still processed and stored by an outside vendor. If you have commitments to clients, check them against the commercial terms.
- Offboarding still needs a process. In a test we ran on a Team account, artifacts an employee had shared stayed available after the employee was removed, but without an owner. We wrote about it in a separate article.
How to switch without stopping work
- Map. Ask employees who uses Claude, from which account, and which systems it is connected to. No blame, or you will not get answers.
- Open an organization. A Team account on the company domain, with at least two owners. A single owner is the same problem at a different scale.
- Set up connectors before adding people. It is easier to open gradually than to close after everyone is used to it.
- Move what matters. An employee whose personal account is registered to their work email can move chats, projects and files to the organization from settings. Custom Skills, Claude Docs and app connections do not move, so download them first.
- Write a one-page policy. What may be uploaded, which tools are approved, and what happens with client data.
- Set a date. From that day, work from personal accounts is not allowed. Without a date, the transition never ends. On Team you can also verify the domain and block new personal accounts from being created on it.
- Add Claude to the offboarding process. Before the user is removed, the employee shares their private projects with edit access. After removal they are no longer accessible to the rest of the team.
FAQ
The employee pays for Pro and turned training off. Isn't that enough?
That solves only the training question, and only as long as the setting stays off. The account still belongs to the employee, the organization cannot see which systems it is connected to, and on the day they leave everything goes with them.
Does Anthropic train models on data from Team or Enterprise accounts?
Not by default. The organization plans are governed by the commercial terms, and the change to the consumer terms does not apply to them.
Team or Enterprise?
For most small and mid-sized organizations, Team is enough to start. Move to Enterprise when you need audit logs, automated user management with SCIM, control over the data retention period, or more than 150 seats.
We are three people. Is this relevant?
Yes. Team starts at two seats, and the question of who holds the knowledge matters just as much for a small business.
What is the difference between Claude Pro and Claude Team?
Pro is a personal account under consumer terms: the employee owns the account and decides whether content is used for training. Team is an organization account under commercial terms: no training by default, with central billing, SSO, connector management and projects shared across the team.
Can we reimburse employees for Pro instead of buying Team?
You can, but it only changes who pays. The account still belongs to the employee, under consumer terms, with no central management and no organization access to what was built in it.
What happens to Claude chats and projects when an employee leaves?
On a personal account everything stays with the employee. On Team or Enterprise, removing the employee ends their access to the organization's account. Removal does not delete their data. Their chats are no longer accessible to the rest of the team, even if they were shared, but the Primary Owner can export them.
Their private projects are not accessible to others after removal. A project shared with the organization stays available. So before removal, the employee should share important projects with edit access (Anthropic's documentation).
Can my manager see my chats on an organization account?
Team members cannot see chats you have not shared. The organization's Primary Owner can export the organization's data, and the export can include users' chats and uploaded files, including Incognito chats (sources: who manages the data, Incognito chats).
Treat the organization account like your work email: it belongs to the organization.
Can chats and projects be moved from a personal account to an organization account?
Yes, provided the personal account and the organization account are registered to the same email address. Chats, projects, files and memory move. Custom Skills, Claude Docs and Claude Sheets, and app connections do not.
The move is one-way: the personal account is closed, and the organization gets access to everything that moved (migration guide).
Is it allowed to use Claude Code from a personal account on company code?
Technically yes, but the consumer terms apply. On Free, Pro, Max and Ultra, Claude Code sessions are also used for training when the setting is on. For company or client code, work from the organization account, where the commercial terms apply.
Sources and test date
Details were checked on November 13, 2026. Anthropic's plans and terms change, and we will update this article when they do.
- Claude plans and pricing
- Anthropic: Updates to our consumer terms and privacy policy
- Claude Code: data usage
- Anthropic: What happens to a user's data when they are removed from an organization
- Anthropic: Who owns and manages the data of my Team
- Anthropic: Move your personal Claude account to a Team or Enterprise organization
- Anthropic: Incognito chats and organization data exports
- Anthropic: Claim and migrate accounts on your domain