Skip to content
Call wiki

How do teammates use what you build with Claude?

Last updated 2026-08-18 · Confidence: documented — Anthropic support articles, Claude Tag and Claude Code docs, and Vercel docs, all fetched today.

Set up Claude Tag once as a Claude-org Owner and everyone in a Slack channel can use it with no per-user setup; artifacts and projects on Team/Enterprise plans share inside the organization only — a public page needs external hosting.

Claude Tag: one setup, the whole channel uses it

Section titled “Claude Tag: one setup, the whole channel uses it”

Claude Tag is Anthropic’s @Claude in Slack, in beta on Team and Enterprise plans. Tasks run in an ephemeral Anthropic-hosted sandbox — created when a conversation starts, discarded when it goes idle, so one sandbox per conversation, not per action (see Agent isolation).

Setup is role-gated on both sides: a Slack workspace admin installs the app, then only a Claude-org Primary Owner or Owner — not the Admin role — provisions Claude’s identity, connections, and channels at claude.ai/admin-settings/claude-tag. After that, what Claude can reach depends on the channel, not on who tags it, and channel work bills to the organization.

The earlier Claude Code in Slack (/install-slack-app) runs each session under the individual user’s account and repos; Anthropic is retiring it on Team/Enterprise in favor of Tag, and it remains the path on Pro/Max.

Artifacts: org-only on Team plans, public on individual plans

Section titled “Artifacts: org-only on Team plans, public on individual plans”

On Team/Enterprise, artifacts can only be shared within your organization — public publishing isn’t offered, and viewers must log into the org account (plus have project access, if project-born). On Free/Pro/Max, publishing makes the link public to anyone. For a genuinely public page, deploy externally: Vercel production domains are public by default; protecting production needs Pro/Enterprise.

Projects and sessions

Section titled “Projects and sessions”

Sources

Section titled “Sources”