The whole hunk
from line 130, old and new numbered
/
lines
from line 130
130130 <a className="tm-qrow" href="/docs/docs/claude-tag/users/use-cases">
131131 <span className="tm-qrow-text">
132132 <span className="tm-qrow-q">What is Claude Tag good at?</span>
133 <span className="tm-qrow-sub">Use cases for coding, data, incidents, and GTM</span>
133 <span className="tm-qrow-sub">Use cases for coding, data, incidents, and go-to-market</span>
134134 </span>
135135 </a>
136136
from line 174
174174
175175If Claude Tag is in your channel, you can use it now. (If it isn't there yet, an Owner in your Claude organization runs setup: see [Set up Claude Tag](/docs/claude-tag/admins/setup-overview).) Anyone in the channel can hand it work, and channel work bills to the organization, not to you.
176176
177What it can reach depends on the channel you're in, not on who you are. The fastest way to find out is to ask it: `@Claude what can you access from this channel?` Or, if you're signed in to your Claude organization, click **Configure** in the footer of any Claude reply to see the channel's connections.
177What it can reach depends on the channel you're in, not on who you are. The fastest way to find out is to ask it: `@Claude what can you access from this channel?` Or, if you're signed in to your Claude organization, click **Configure** in the footer of a Claude reply in the channel to see its connections. Replies in org-shared channels have no Configure link.
178178
179179The one exception is a DM, where it runs on your own claude.ai account instead of the channel's setup. Owners can disable DMs organization-wide; see [Allow or disable direct messages](/docs/claude-tag/admins/restrict-access#allow-or-disable-direct-messages).
180180