Claude in a private channel

Some of your work includes information only specific people should see, like people matters, finance, legal work, or a customer escalation with confidential detail. You already keep that in a private channel, and Claude keeps the same boundary.

What you can do in a private channel

If you want that same team help on work only a specific group should see, ask Claude in that group's private channel.

• The same channel work, for members only: everything lesson 3 describes works here for the channel's members: threads anyone in the group can correct or continue, this channel's history and connected tools, untagged replies and routines.
• Tools connected for members only: a tool can be connected to this channel alone, the same way tools are connected to a public channel. In a private finance channel, for example, your billing system may be connected: only the channel's members can have Claude use it, and Claude can do only what the account created for it is allowed to do, which is kept to the least access the work needs.
• What the workspace has already taught Claude: the channel benefits from the workspace notes Claude has saved in public channels, without adding to them.

Protecting your privacy and data

The channel's boundary is Claude's boundary

A private channel's boundary applies to Claude the way it applies to people.

• Only members can have Claude read or act here: from any other channel or DM, Claude behaves as if this channel, its tools, and its memory do not exist, and its replies here are visible only to the channel's members.
• What Claude learns here is saved to this channel only: Claude saves it to this channel's notes and never to workspace notes, so confidential context cannot surface in someone else's channel.
• Tools connected here are for members only, with the access they were given: whatever that account can read is available to every member through Claude, so the member list is the access list. Keep it tight.
• Every action is attributable: Claude acts under its own account in the team's connected tools, so the tool's own log shows what Claude did and when. How agent identity works has the detail.
• Guests and shared channels are handled by your admin: whether Claude answers in a channel with guests, or one shared with another company, is an admin setting (guest channels). Where it does answer, Claude keeps to that channel and does not search the rest of the workspace from there.

Try it

Before you move on

Key takeaway: a private channel's boundary is Claude's boundary; the same work, kept to its members.

After practicing: You will have run one sensitive task in a private channel, visible only to its members.