Your Team Is Using AI on Personal Accounts. That's the First Problem to Fix.

Walk through most small companies right now and you'll find the same thing: people are already using AI, on their own personal accounts. A free ChatGPT login here, somebody's personal Claude subscription there, a few of them quietly expensing it, plenty of it invisible to the owner entirely.

Your client list, your financials, your strategy, your customer emails, all of it getting typed into accounts the company doesn't own, can't see, and can't control. There's a name for this now. It's called shadow AI, and it's the first thing to fix before you think about anything else.

Once your team is on the right footing, the next question is what to share across everyone and what to keep individual. Both matter. Take them in order.

TL;DR: Move the team onto business AI accounts, then draw one line: shared at the team level, individual at the user level. Company knowledge, brand voice, process skills, and shared connectors belong to everyone. Personal memory, role instructions, and private connectors like email stay with the person.

• Shared: company facts, voice, process skills, team connectors.

• Individual: personal memory, role prompts, email and calendar.

• First step: business accounts, because personal logins walk out the door with people.

First, get everyone onto business accounts

Before you decide what to share, make sure your team is using AI the company actually owns. Personal accounts create three problems that have nothing to do with how good the AI is.

You don't own it. When someone builds up a personal AI account around your business, all that context lives in their account, not yours. They leave, it leaves with them. You can't retrieve it, and you can't shut off their access to everything they loaded in.

You can't see or govern it. No admin view, no record of what's being used or shared, no way to set rules or pull access when you need to. If a client ever asks how their data is handled, "I'm not totally sure, my team uses their own accounts" is not an answer you want to give.

Your data protections depend on settings you can't enforce. On consumer accounts, what happens to your data varies by vendor and plan, and some of it can be used to help train the models. You're trusting each employee to have the right toggle flipped. That's not a control. That's a hope.

The fix is business accounts: ChatGPT Business, Claude Team, Google Gemini for Workspace, Microsoft Copilot, the company-owned tiers. On these plans the vendor contractually does not train its models on your data (Anthropic doesn't train on any paid Claude plan, OpenAI doesn't on Business or Enterprise, and Google keeps your Workspace data out of model training), the company owns the workspace, and you manage who has access from one place. The exact data rules vary by vendor and tier, which is the whole point: on a business account you get them in writing and you control them, instead of trusting a dozen personal settings.

If you're in a regulated field, healthcare, financial services, anything with client confidentiality on the line, this is where you step up to an Enterprise plan. That tier adds the audit logs, data-retention controls, and the signed HIPAA agreement (a BAA) that compliance actually requires. For a vet clinic or an accounting firm, that's not optional.

And don't let the switch scare you. The usual worry is that moving to a business account means losing everything you've built or spending a weekend re-teaching the AI from scratch. It doesn't. Your business context, the company description, the brand voice, the processes, is mostly documents and instructions, and that moves over in an afternoon. There are proven prompts for porting the rest: ask your current AI to write up everything it knows about you and your business, then paste that summary into the new account to bring it up to speed. The same trick moves context from ChatGPT to Claude or Gemini and back. You're transferring a briefing, not starting over.

This is step zero. Everything below sits on top of it.

What belongs shared, at the team level

Once you're on business accounts, the next call is what every person shares versus what stays their own. Start with the shared layer: anything that should be the same for everyone.

Your company knowledge and identity. Who you are, what you sell, your clients, your standards. This is the org-level instruction layer, written once and shared, so every person's AI starts from the same accurate picture of the business instead of whatever they typed in from memory.

Your brand voice. If marketing, sales, and the front desk are all generating customer-facing writing, they should pull from one definition of how your company sounds. Otherwise you get twelve subtly different brands. One shared voice, everyone on it.

Your process skills. The recurring workflows a department runs, your intake process, your monthly close, your proposal format, built once as shared skills so the whole team runs them the same way. This is the team version of the functional workstations from The Three Workstation Types.

Shared connectors. The systems the team works from together: the CRM, the accounting software, the shared drive. Connect them once at the team level instead of having each person wire up their own.

The thread through all of these: if it should be consistent across people, it belongs shared. Consistency is the whole reason a team environment exists.

What stays individual, at the user level

Anything specific to one person stays with that person.

Personal memory. What the AI has learned about how you work, your habits, your shortcuts, your preferences. That's yours, and it shouldn't bleed into everyone else's setup.

Role-specific instructions. Your job, what you're responsible for, how you like things delivered. The CFO and the office manager work from the same company knowledge but need different things from their AI day to day.

Your own calendar and email. Personal by definition. Your inbox connects to your workstation, not the team's.

This is the personal workstation from C5, sitting on top of the shared layer. The shared environment gives everyone the same foundation; each person's individual setup adds the part that's just theirs.

Why the line matters more than it looks

Put the wrong things in the wrong place and you pay for it two ways.

Share too little, and everyone privately rebuilds the same company context, badly. You get drift: ten versions of your brand voice, five interpretations of your process, no single source of truth, and a lot of wasted hours. Nobody's working from the same page because there is no same page.

Share too much, and you get the opposite problem. Personal inboxes and individual preferences dumped into a shared space, sensitive information visible to people who shouldn't see it, and a setup so cluttered with everyone's individual stuff that it's useful to no one.

What trips people up

Three patterns, all avoidable.

Staying on personal accounts because they're already set up. The switch to business accounts feels like a hassle, so it gets put off, even though the move is easier than most owners expect. It's the single highest-value move on this list, and it gets harder the longer you wait and the more context piles up in accounts you don't own.

Oversharing personal context. Dumping individual inboxes, personal notes, and one person's preferences into the shared environment. Keep the shared layer to what should be common. Personal stays personal.

No owner for the shared layer. A shared environment with nobody maintaining it rots the same way a project does. Someone needs to own the company knowledge, the brand voice, and the shared skills, and keep them current.

Where to start this week

Find out what your team is actually using. Ask, plainly, which AI accounts people are on and what they've been putting into them. Most owners are surprised, both by how much AI is already in use and by how much of it is happening on personal logins.

That answer tells you how urgent step zero is. Get everyone onto a business account, then write down the one thing that should be identical for everyone but currently isn't, your company description, your brand voice, your intake process, and put it in the shared space. You've now fixed the ownership problem and drawn the first shared line. For the full decision tree on where every new piece of knowledge should live, that's the next piece.

Questions we hear about team AI accounts

Why not just let everyone use their personal ChatGPT?

Three reasons: the knowledge each person builds leaves when they do, nobody works from shared standards, and company data ends up under consumer terms instead of business ones. The fix costs a plan upgrade, not a project.

What belongs in the shared layer?

Anything every employee should inherit on day one: who the company is, how it talks, and the skills that run your standard processes. When you’re not sure where a new piece belongs, the sharing decision tree settles it in five questions.

Do Claude, ChatGPT, and Copilot all support this split?

Yes. All three offer team plans with shared workspaces and individual logins inside them. The layers you’re splitting are the same ones covered in The Six Layers of an AI Setup That Actually Works.This is part of the Practical AI Toolkit series. Hub: Cornerstone 2: The AI Workstation Playbook. Read next: The Sharing Workflow Decision Tree.