A worker with its own name

Slack in six lines

The firm talks in Slack, a chat app for teams. If you have not used it, this is all you need.

• A channel is a room for one topic. Its name starts with #.
• A private channel is a room that only invited people can enter or see.
• A message is what someone writes in a channel. Everyone in the channel can read it.
• A thread is the set of replies under one message. It keeps one conversation together.
• Writing @ and a name calls that person. Writing @Claude calls the worker.
• A one-to-one message is a private chat between two people, outside any channel.

A worker in the channel

Anthropic's Claude Tag puts Claude into a team's Slack channels. It was in public beta, on Team and Enterprise plans only.¹ Nisha, as the Owner of the firm's Claude organization, set it up one evening. She added Claude to a private channel called #lakeshore-work. The channel had three human members: Nisha, Sana and Hamza.

From then on, any of the three could write @Claude in the channel and hand it work. It answered in a thread under the message, where all three could read every step.

Its own accounts

This was the change Nisha had wanted since that Thursday night with Mark's bridge.

In her old project, anything the worker did through a connector appeared as her. In a Slack channel, Claude acts under its own service accounts, not as the person who asked.² Anthropic's advice was to give it a dedicated account in each tool, not anyone's personal login.

So Nisha created a mailbox for the worker, reports@, at the firm's own address. An email from the worker would now arrive from reports@, not from Nisha. Dana would be able to tell the worker's mail from Nisha's own.

Two things stayed personal.

• One-to-one messages. If Hamza wrote to Claude in a private one-to-one message, that session would run on Hamza's own account, and its work would appear as Hamza's.³
• A member's own connectors. In a channel, Claude can also use a connector from a member's own Claude account, but only for that member's own task, after the member allows it. That work is recorded under the member's name, not the worker's.⁴

So there were two kinds of access in the firm's Slack: the shared access that belonged to the worker and the channel, and each person's own access. The firm agreed to keep client work in the channel, and that nobody would connect a personal email account. That agreement was a rule, not a setting.

What the channel holds

In Claude Tag, access belongs to a place, not to a person. An admin chooses where each connector applies, from all of Slack down to one channel.⁵ Nisha applied three things to #lakeshore-work and nowhere else.

Email was not among Claude Tag's ready-made connectors. Nisha added the mailbox as a custom connector to the firm's email service.⁶

The bank key was the one she had worried about most. She typed it in once. After that, even she could not see it again. The key is kept outside the worker's desk and added to each request on its way out, so the worker itself never holds it.⁷

Nothing lasts at the desk

Each Slack thread gets its own borrowed desk. When a thread goes quiet, the desk is released, and any file that existed only there is gone.⁸ Nisha had learned this lesson with her project's Library. Here there was no Library.

So she wrote it into the channel's instructions: post every file in the thread, and save a copy to the shared drive with its date. The thread and the drive were outside the desk. They would still be there on Monday.

Next, Two routines and one rule.

Sources for the product facts in this story are given in full in the exhibits.