One read of Claude Documentationclaude-docs-20261002T000722Z
3 pages moved out of 259 read.
Pages moved
3
significant first
Pages read
259
in this capture
Captured
00:07 UTC
Corpus hash
cd2e45a6750e
corpus-hash
What this read moved
1-3 of 3claude-tag/concepts/personal-connectors Changed · +18 / -0 lines
### Example calendar request in a channel ### What channel connections can reach
from line 28
2828
2929To add or remove connectors on your account, open the **Customize > Connectors** page on claude.ai; see [connectors on claude.ai](/docs/connectors/getting-started) for setup.
3030
31### Example calendar request in a channel
32
33This example shows what you see when a request you post in a channel needs your calendar. Google Calendar is connected on your claude.ai account.
34
351. You post `@Claude find a free 30-minute slot on my calendar Thursday afternoon` in a channel.
362. Claude replies in the thread with a prompt only you can see, asking whether it may use your connectors for this request.
373. You choose [**Allow with review**](#approve-connector-use).
384. Claude reads your calendar with your account's access and shows you the slot it found.
395. You approve the slot, and Claude posts it to the thread.
40
41If a teammate posts the same request, Claude can offer to use the calendar connected on their own claude.ai account. Claude never uses your connector for their request.
42
43### What channel connections can reach
44
45Connections an admin attached to the channel give everyone in the channel the same access. They use the account the admin set up for Claude in each service, so Claude reaches whatever that account can reach, whoever asks.
46
47If a channel connection can open a document your own account can't, Claude can still read and summarize it in that channel when you ask. See [agent access](/docs/claude-tag/concepts/agent-identity#agent-access) for how admins limit what a channel can reach.
48
3149## Control connector use
3250
3351### Approve connector use
claude-tag/users/troubleshooting Changed · +17 / -0 lines
### Can't access this organization when I connect my Claude account
from line 608
608608
609609Once the limit is raised or the period resets, mention Claude in the same thread to retry.
610610
611### Can't access this organization when I connect my Claude account
612
613**What you see**
614
615You select **Connect Claude account** in Slack, and the claude.ai page that opens is titled **Can't access this organization**, with this message:
616
617> You don't have access to this organization or it doesn't meet the requirements for Claude for Slack. Contact your organization admin to request access.
618
619**What it means**
620
621Your Slack workspace is connected to a Claude organization, and the connect link opens claude.ai already pointed at that organization. The most common cause of this page is that the claude.ai account signed in on the browser where it opened isn't a member of that organization.
622
623**How to resolve**
624
6251. Check the address after **Signed in as**. If it isn't your work claude.ai account, select **Sign in with a different account** on that page, sign in with your work account, then select **Connect Claude account** in Slack again.
6262. If the address is already your work account, ask your Claude admin to check that you're a member of the organization, then select **Connect Claude account** again.
627
611628## DMs aren't working
612629
613630DMs run on your own Claude account rather than the organization's agent. They need a qualifying seat (a seat that includes Claude Code, or on the Enterprise plan a **Standard** or **Usage-Based Chat** seat when the member also has Cowork), and they use your personal connectors rather than the channel connections. If channels work but DMs don't, first check that your Claude account is connected; DM `@Claude` and it prompts you to connect if it isn't.
government/changelog Changed · +4 / -0 lines
from line 2
22
33> Release notes for Claude for Government
44
5<Update label="2026.10.01.1">
6 * Added a **New members start here** option to self-managed seat tiers, so you can pick the tier new members start on.
7</Update>
8
59<Update label="2026.09.29.1">
610 * Changed directory sync so that a member who leaves a group mapped to a self-managed seat tier with no seat limit keeps that seat tier until another group's mapping or an admin moves them.
711 * Added the ability for tenant administrators to grant and remove the Primary Owner role in an organization that doesn't manage its own billing account.