Site-level permissions disabled? First, check what still works.

The warning does not always mean access is broken

There are two different problems to separate. In one, Claude asks permission for each action and continues after you approve. In the other, it cannot read or interact with the site at all. Spending time reinstalling an extension will not tell you which problem you have.

A June 2026 firsthand report documents the exact warning on Facebook alongside single-action approval buttons. That establishes one observed example, not a universal rule for Facebook, social networks, or every account. Anthropic separately documents websites that require approval for each action. The page below uses that official distinction without claiming an unpublished list of restricted sites. Reported example · Official permissions guide

If one action works, use the permission the site offers

Read the requested action and confirm that the domain is the one you intended. If it is safe, permitted, and necessary, approve that specific action. If Claude completes it and asks again for the next step, record that behavior as repeated approval—not total access failure.

A missing ongoing-approval option is not a reason to grant the extension access to every website. Do not use 'Skip all approvals' as a troubleshooting shortcut. Keep your task small enough to supervise, and decline anything that exceeds it. If the repeated prompts make a task impractical, complete the task manually or ask for a draft from permitted, nonsensitive material that you deliberately provide.

If the prompt seems inconsistent with a previously working task, capture its wording and date. Product behavior changes; support can investigate an unexpected restriction without you weakening the rest of your browser's settings.

If access fails completely, check the right permission layer

Chrome extension site access, Claude's approvals, and your organization's controls are separate checks. A website's camera or notification permission is a different setting again. Changing an unrelated permission adds noise to the diagnosis.

In Chrome, open Extensions, then Manage extensions, and find Claude. Confirm it is enabled. In its Details, review the site-access options shown for your version. If you are authorized to change them, grant only the access needed for the intended site. Chrome documents controls for access when selected, specific sites, or all sites. Chrome extension guidance

In Claude's side panel, use the three-dot menu and Extension settings to review approved sites and permission history. These settings help inspect prior approvals; do not assume they let you override every restriction. Anthropic's current interface includes both classic and Cowork side panels, so older screenshots may not match yours.

If a setting is locked, involve the right administrator

Check Chrome's menu for a managed-browser notice, or type chrome://management into the address bar. A managed browser can have restrictions set by your organization. Inspection is useful; removing management or changing device policy to get around a restriction is not an appropriate fix. Google's managed-browser guidance

Claude Team and Enterprise organizations can also control extension availability and allowed or blocked sites. A working Chrome installation does not establish that your Claude organization permits the intended site. Ask the relevant owner or administrator to review the policy for the actual business task. Browser IT and the Claude organization owner may be different people. Anthropic's admin controls

• Describe the task and why the site is needed.
• Give the domain, the exact warning, and whether individual approval works.
• Ask whether the workflow is permitted and which approved method to use.
• Do not attach customer data, session cookies, passwords, or an unredacted full-screen capture.

If the extension is connected but still cannot see the page

For ordinary access failures, Anthropic recommends refreshing the page, checking that the extension is enabled, confirming site permission, and allowing complex pages time to load. Its troubleshooting guide also identifies default blocked categories and organization restrictions as possible causes. An intentional block should remain in place. Official troubleshooting

A connection error between Chrome and Claude Desktop or Claude Code is a separate problem. Note the exact connection message and which application started the task. Follow the official connection guidance for that application rather than repeatedly changing site permissions.

Make one authorized change at a time, then repeat the same harmless request. Write down whether the behavior changed. Avoid clearing all browsing data, disabling security extensions, or reinstalling software as a first response to a message about site-level approval.

Use a small verification task and save the result

For a site you are allowed to use, choose public, nonsensitive information already visible on the page. Ask Claude to identify the page title and summarize a short visible section. Do not use a customer record, bank account, unpublished document, or message-send action to test whether access works.

Record one of three outcomes: the action succeeds after individual approval; the site is blocked or controlled by an administrator; or access still fails for an unexplained reason. This narrows the next step without pretending the diagnostic has inspected your computer.

A useful support request says: 'On this date, while using this Chrome version and Claude surface, this domain showed this exact warning. Individual approval does or does not work. My browser is or is not shown as managed. I tried these specific checks, with these results.' Keep identifiers and screenshots limited to what support needs.