Restrict where Claude Tag operates changedclaude-tag/admins/restrict-access
Nearest release: v2.1.242, published under an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+8added
Lines−0removed
From line
55
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits50to this page, all time
### Restrict who can link a Claude account by email domain
The whole hunk
from line 55, old and new numbered
/
from line 55
5555
5656<Warning>On a Slack Enterprise Grid whose workspaces are paired to different Claude organizations, one organization's access settings govern the entire grid, so your restrictions may not be enforced in your own workspaces.</Warning>
5757
58### Restrict who can link a Claude account by email domain
59
60On Enterprise plans, if your organization belongs to a parent enterprise organization, you see one more toggle in the same **Manage** dialog, **Restrict to your verified domains**. It needs an Owner to change and is disabled while Claude Tag is off for the organization. The check uses the enterprise's verified domains, which every organization under the enterprise shares.
61
62When the toggle is on, a Slack user whose profile email isn't on one of the enterprise's verified domains can't link a Claude account to this organization; the sign-in is refused.
63
64<Warning>Turning this on in any one organization also stops Slack users on a verified domain from linking a Claude account to any organization outside the enterprise.</Warning>
65
5866## Control where Claude Tag operates
5967
6068The restriction toggle decides who can use Claude. The controls in this section decide where it works at all, from one channel up to a workspace, and which generation answers in each scope (a scope is a channel, a workspace, or your whole organization).
No line in this hunk matches that.