What
A session started with the restricted option is now treated as non-default, the same way skipping permission prompts or allowing bypass already were.
Evidence
Boolean(n.restricted) ||
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundlerestricted
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Customize Claude Tag touched a line naming restricted after this was published.
The Configure page also shows the channel's resolved access. Its **Tools and access** tab lists the channel's resolved connections and any allowed domains. Members can see those lists but not change them there. The same tab's **Plugins** c…claude-tag/admins/customize see the edit
Confirmed since
Anthropic's documentation has since written up restricted, on Give Claude access to your tools.
A Datadog API key, for example, makes the API reachable, and a Datadog plugin tells Claude which endpoints answer which questions. Sessions in covered channels pick up attached plugins automatically, with nothing to install or enable. Chan…claude-tag/admins/add-connections see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up restricted, on Give Claude access to your tools.