Loading
In this lessonBy the end, you’ll be able to
  • Explain which parts of your configuration carry over to a new product automatically
  • Walk the three questions you re-run for the arrival of any new Claude surface
  • Answer the three questions on a surface you don’t use yet

New products arrive regularly, and you may find yourself facing these decisions once again. This lesson walks through the process for a new arrival: what carries over on its own, and the three questions you re-run per product.

What carries over

Most of your structure carries over unchanged, because it reflects your objectives, not the state of the products. That covers:

  • Your organization boundary (Lesson 4)
  • Your groups and roles (Lesson 5)
  • Your governance posture (Lesson 8)
  • Your caps (Lesson 9)
  • Your visibility pieces (Lesson 11)

Re-check those settings against anything new about the surface: the carry-over is the typical outcome, not a guarantee.

The edge case is a genuinely new kind of product, one that works somewhere your controls do not currently look; it can add a question of its own, the way agent surfaces added task-scoping to spend guidance. The three questions below cover everything else.

The three questions

  • Who gets it? This is the Lesson 6 decision, replayed: consider which groups’ daily work calls for it, and in what phase.
  • What does it carry? Does it bring settings or connectors of its own, so those earlier lessons re-run for it, or will it require more specific grants?
  • Does it move risk? Does it give Claude a new kind of reach: into a new class of data, or with a new degree of autonomy, or in front of new people? If it does, the risk owner should be consulted.

Pluto’s latest arrival: Claude Tag

Pluto is considering a rollout of Claude Tag, a way for teams to work with Claude inside Slack, in beta on the Team and Enterprise plans.

  • Setup and use: a Primary Owner or Owner sets it up, adds it to a first set of channels, and connects it to the tools, data, and codebases they choose; members can then add Claude to other channels and tag Claude there to delegate tasks while they focus on other work, and Claude builds context from the channels it’s in.
  • In a channel: Claude Tag works under its own identity rather than as the person who tagged it, with the access attached to that channel’s scope, so everyone in the channel gets the same capability; a member can also let it use their own connectors for their own tasks, and the results post where the whole channel can see them.
  • In direct messages and the assistant panel: Claude carries the member’s own account capabilities, and the usage counts against the member’s own seat and its limits rather than the Claude Tag balance; group DMs, and by default one-to-one DMs from members without a Claude account (other than Slack guests), for a limited time per member, bill to the organization like a channel.

Pluto is four months into its Claude Enterprise rollout and ran Claude Tag through the three questions:

QuestionWhat Pluto decidedHow it relates to Pluto’s objectives
Who gets it?By default anyone in the Slack workspace can use Claude Tag, even without a Claude account, so Pluto turned on the role restriction to grant it by role, like any other surface (Lesson 6; every built-in role includes it, so only a custom role without it keeps a member group out), and switched Claude on only in the channels of the units whose work already runs in Slack threadsThe surface goes where the groups’ daily work already happens, rather than to every channel
What does it carry?Configured fresh for the channels that got it, because it is channel-scoped and little carries over from the per-member setup (your organization’s model access still applies); channel usage is billed to the organization rather than to individual seats, with its own limits and no upper bound until one is set, so the spend owner set those alongside the existing capsChannel-scoped access is new, so the earlier per-member grants can’t cover it; organization-level billing keeps it on the spend owner’s review rather than under member caps
Does it move risk?Yes: as the beta stands, Claude carries the channel’s access no matter who is talking to it, so Pluto kept the default that blocks Claude in channels with a guest present, which also keeps it out of channels shared with other companies through Slack Connect, and kept Claude Tag off for Payments & Trust, its regulated group, the same tighter posture it holds elsewhere; the risk owner signed the choiceGuest and Slack Connect channels put people outside the organization in front of Claude’s channel-scoped access — the kind of new reach that goes to the risk owner

The interactive widget below runs Claude Tag through the three questions at Pluto and shows which of Pluto’s existing decisions reopen while the rest carry over.

Loading

Set up resources

To learn more about Claude Tag and where to go when a new surface rolls out, you can start with the resources below.

Lesson activity

Pick one Claude surface your organization does not use today, and run the three questions in your companion. If your organization already uses every surface, review the interactive above for what the next one will ask of you.

→ Record this in the work-along companion, section Lesson 14.

Downloads

  • Work-along companion (Word)

    The editable Word version of the rollout plan you fill in lesson by lesson.

    Download
  • Work-along companion (PDF)

    The same rollout plan as a fillable PDF.

    Download

What’s next

The course closes with a short quiz that checks the concepts have landed. Your completed companion, not a score, is the evidence you’re ready.