When managers suddenly want everything documented — every decision, every email template, every way a difficult customer gets handled — it feels like micromanagement at first. Then the more unsettling explanation comes into focus.
A pattern that has surfaced repeatedly across remote and hybrid workplaces: companies quietly launch "knowledge base initiatives," asking employees to export Slack conversations, write up their processes, and record how they solve problems. The stated reason is institutional knowledge. The actual reason, in a growing number of cases, is AI training data.
One documented case involved a company that created an AI chatbot trained entirely on a single employee's emails and Slack messages — without that employee's knowledge. The company used the bot to handle the employee's job while keeping them on payroll, then slowly phased them out. By the time the employee understood what had happened, the company had months of training data and a working replacement.
The documentation requests weren't about knowledge management. They were about data collection.
The thing nobody talks about is how easy this actually is.
Slack messages are just text. Emails are just text. Any company with admin access to its own workspace — which every company has — can export everything. Bulk-download thousands of conversations in minutes. Feed them into an AI model. Train it on how a specific employee writes, thinks, solves problems, and responds to angry customers at 2 PM on a Tuesday.
The unsettling part: it's not illegal. Not yet. The company owns the Slack workspace. The company owns the email server. Legally, they can do this. The ethical question is a different conversation — one that's largely not being had.
Across customer support, sales, technical writing, and content creation — any job where communication *is* the work — the same story keeps surfacing. A manager who suddenly wants everything documented. A new "AI assistant" that sounds suspiciously like a specific coworker. A colleague who gets laid off right after the company launches an AI tool that does their exact job.
In one case, a support professional discovered her company had created an AI agent trained on two years of her support tickets. She wasn't told. She found out when a customer mentioned talking to "the new AI." She had been training her own replacement without knowing it.
This is not a speculative scenario. Companies are doing this because it works. An AI trained on a specific person's actual communication patterns outperforms a generic model. It sounds like that person. It knows their shortcuts, their style, their problem-solving patterns. And for remote workers, there's no ambient awareness that anything is happening — no visible signs, no overheard conversations. Work continues. Communication continues. The training data accumulates.
So what do you actually do about this?
The depressing baseline: you probably can't stop your company from using your data. But you can know when it's happening. Bulk access to messages, unusual API activity, anomalies in who is accessing what — these things are visible if you know where to look.
Pay attention to documentation requests. If your manager suddenly wants everything in writing, if there's a new knowledge base initiative, if you're being asked to record your processes — ask why. Not in a paranoid way, just directly: "What's this for?" Sometimes it's legitimate. Sometimes it isn't.
Check your Slack and email settings. Find out who has admin access. Understand what data is being exported and where it goes. This isn't paranoia — it's job security hygiene.
Talk to coworkers. If the pattern is visible to you, it's probably visible to others. There's informational value in knowing whether this is an isolated request or a company-wide shift.
If you're in a customer-facing role — support, sales, writing — the risk is higher. Your communication is the product. It's the easiest thing to train an AI on. Think carefully about what you document and how.
More strategically: think about what makes you irreplaceable in ways that don't live in Slack. Not the ability to write a support email or handle a complaint — those are being automated. The things that resist automation are judgment, the ability to read a situation accurately, creativity in solving edge cases, relationships, and the instinct to know when a rule should be broken. Those don't show up in an export file.
A tool built to surface exactly this kind of activity — suspicious access to Slack or email, bulk exports, anomalous behavior — is available at https://ai-shadow-shield.vercel.app. It won't prevent a company from collecting the data, but it provides visibility: access logs, alerts, documentation if you ever need it.
But the core defense is attention. Notice when you're being asked to document everything. Notice when new AI tools appear that sound like specific people on your team. Notice when your role starts to feel oddly redundant. Notice when the company seems more interested in capturing how you work than in what you produce.
Once you notice, you can act — ask questions, protect yourself, and make sure that if a replacement is being built, you see it coming before it's finished.