Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One capture · claude-docs

One read of Claude Documentationclaude-docs-20261014T023709Z

1 pages moved out of 265 read.

Pages moved 1 significant first
Pages read 265 in this capture
Captured 02:37 UTC
Corpus hash 83fb5c5233ab corpus-hash

What this read moved

1-1 of 1

claude-tag/admins/attach-to-scope Changed · +1 / -1 lines

from line 96
9696A rule's pattern has its own constraints:
9797 
9898* **Pattern syntax**: a rule's pattern follows the same syntax as the other [channel name patterns](/docs/claude-tag/admins/restrict-access#block-or-auto-join-channels-by-name), lowercase with `*` matching any run of characters and `?` matching exactly one
99* **Number of rules**: each scope holds up to 20 channel rules
99* **Number of rules**: each scope holds up to 50 channel rules, and a rule with more than one bundle counts once for each bundle
100100* **Organization patterns**: on a workspace's page, the **Auto-join channels** table also lists the organization's patterns, marked **Org-wide**. You can attach a bundle to an **Org-wide** pattern from the workspace's table, and that rule covers only the workspace's matching channels. You edit the pattern itself on the **Slack** page.
101101 
102102<Warning>A channel rule grants its bundle in every matching channel Claude is in, now or in the future, and anyone who can rename a channel can move it into or out of a pattern. Keep elevated credentials out of broad patterns, and add a [blocked channel pattern](/docs/claude-tag/admins/restrict-access#block-or-auto-join-channels-by-name) for name shapes that should never carry access; a blocked channel stays off-limits whatever rules match it.</Warning>
Feedback