Owners of a GitHub organization sometimes get an email titled "[GitHub] Claude is requesting updated permissions." It is a notification that GitHub sends automatically when "Claude," Anthropic's GitHub App installed in the organization, adds to the permissions it asks for. If you don't approve, Claude keeps working with its current permissions, but features that need the new permissions may not work.
Key points
- The email
- A notification GitHub sends to the owners of every organization that has a GitHub App installed when the app's developer adds permissions. Claude has not gained anything on its own: the new permissions don't take effect until you approve them.
- If not approved
- Claude keeps working with its current permissions. Features that use the new permissions may not work as expected. You can't pick only some of the permissions: approving means accepting everything requested at once.
- How to decide
- If you use features that run on Anthropic's side, such as Code Review, Claude Tag, plugin auto-sync, or cloud sessions, you will likely need to approve. If you only use Claude Code GitHub Actions in your own workflows, there is little reason to hurry, and you can also switch to your own app with narrower permissions.
Checked against the GitHub and Claude Code documentation on November 14, 2026
1. Check it's real
Don't click the link in the email. Open Claude's page yourself from your organization's settings on GitHub
2. Read what's added
Look at the additional permissions shown and what each one allows (table in section 5)
3. Decide by feature
Approve if the Claude features you use need it; otherwise it's fine to leave it pending (section 6)
1. What the "Claude is requesting updated permissions" email is
The email looks like this (the organization name and ID differ for each organization).
Subject[GitHub] Claude is requesting updated permissions
The GitHub App Claude, which is currently installed on your your-org organization, has updated its permissions and is requesting additional access.(In plain terms: Anthropic changed the list of permissions the Claude app asks for, and your organization hasn't accepted the new list yet.)
You may choose to ignore this request. If you do, Claude will retain its current permissions.(Nothing changes until an owner approves.)
Approval page: github.com/organizations/your-org/settings/installations/ID/permissions/update
Excerpted from the body of an email received on November 14, 2026, with plain-language notes added.
According to GitHub's documentation, when the developer of a GitHub App adds repository or organization permissions, GitHub emails the owners of each organization that has the app installed (or the account holder, for a personal account). The updated permissions don't take effect in that organization until they are approved; until then, the app keeps its current permissions. Changes that reduce permissions, by contrast, take effect immediately.
In other words, the email is a question: Anthropic changed the permission list for the Claude app, so will your organization accept the new list too? It is not a notice that Claude has acquired permissions on its own.
Anthropic also explains in the Claude Code documentation that the app's permission list can change before the features that use it ship, and that when the app requests new permissions, GitHub asks organization owners to approve them, with the old permissions staying in place until they do. Claude's support article (Manage plugins for your organization) adds that plugin auto-sync requires approving Webhooks (read and write) for the Claude app, and that organizations that installed it before this permission was added will see "Claude is requesting updated permissions" on GitHub. However, as of November 14, 2026, we have not found a changelog that shows which permissions were added on which date.
2. How to tell whether the email is real
An email asking you to approve permissions is also a natural shape for a phishing scam that leads to a fake sign-in page. Rather than trusting the email itself, the reliable check is whether you can reach the same page without using the email.
- Sender
The real email comes from GitHub's
noreply@github.com. The displayed sender can be spoofed, though, so this alone doesn't prove it's genuine. - Link target
The approval page is at
github.com/organizations/…/settings/installations/…. Hover over the link, and don't open it if the domain is anything other thangithub.com. - Your own route
On GitHub, open your organization's Settings, go to GitHub Apps under "Third-party Access" in the sidebar, and click Configure next to Claude. This takes you to the same app's settings without using the link in the email.
- App developer
Anthropic's app is named Claude, and its developer is anthropics (github.com/apps/claude). Don't approve an app with a different developer or one that only has a similar name.
- Sign-in prompts
If you're asked for your password or two-factor code on the way to the approval page, confirm that the address bar shows
github.combefore entering anything.
How to navigate the settings is from Reviewing and modifying installed GitHub Apps (GitHub Docs, checked November 14, 2026).
3. What happens if you don't approve, and why you can't approve only part of it
Approve
- All requested permissions take effect in that organization
- Claude features that use the new permissions work
- You can't choose only some of the permissions
Don't approve (leave it)
- Claude keeps working with its current permissions
- Features that need the new permissions may not work as expected
- The request stays pending
GitHub's documentation says both things: if you don't approve, the app keeps its current permissions, and it may not work as expected (Approving updated permissions for a GitHub App). When the email says you may ignore the request, it means nothing breaks right away. Keep in mind that it can be the reason a new feature doesn't work when you try it later.
Approval is all or nothing. The Claude Code documentation says that installing the app means accepting its entire permission list, and that GitHub doesn't allow partial approval. In the GitHub Community, users have reported a single update that bundled Members and Webhooks together with only one button to approve it, and that there is no button to reject, so the only alternative is to leave the request pending (GitHub Community discussion; user reports).
4. Which Claude features use which permissions
Anthropic normally has a single app on GitHub, "Claude." According to the Claude Code documentation, this app is shared by every Claude feature that connects to GitHub, and one app can only have one set of permissions, so even an organization that uses just one feature gets the permissions meant for the others.
| Claude feature | GitHub App | Main permissions used (per Anthropic's docs) |
|---|---|---|
Claude Code GitHub ActionsResponding to @claude, /install-github-app | Claude (can also be your own app) | Read and write on Contents, Issues, and Pull requests |
| Code ReviewAutomatic pull request reviews (Team, Enterprise) | Claude | Checks write access to post results as a check run, among others |
| Auto-fix in cloud sessionsFixes pull requests based on CI results | Claude | Actions and Commit statuses to read CI status, among others |
| Claude TagPull requests for work requested from Slack | Claude | Re-running and canceling workflows, triggering workflow_dispatch, deleting runs, logs, and artifacts, enabling and disabling workflows (Actions), and editing .github/workflows/ (Workflows), among others |
| Organization plugin auto-syncSyncs on push to the marketplace repository | Claude | Repository hooks write access to create a webhook on the repository |
| GitHub integration in claude.aiBrings repositories into chats and projects | Claude | Access to read private repositories |
| GitHub Enterprise ServerGitHub you host yourself | A separate app created on your own server | Separate from Claude on github.com. Permissions are added in your own app's settings |
Sources: Claude Code GitHub Actions (GitHub App permissions section), Code Review, Claude Code with GitHub Enterprise Server, Claude Tag's Configure GitHub access, Sync your organization's plugins from a repository, and GitHub integration (all checked November 14, 2026).
For how cloud sessions themselves work, see What are Claude Code cloud sessions?; for Claude Tag, which you use from Slack, see What is Claude Tag?; and for the difference between reviews run with a local command and the app-based Code Review, see What is Claude Code /code-review?
5. How to read the permission list: what each one allows and which are powerful
The Claude Code documentation lists the permissions held by the Claude app on github.com (checked November 14, 2026). Below, each one is paired with what it allows on GitHub, based on GitHub's own descriptions of the permissions. The strength ratings are this article's own three tiers: "write access with broad impact," "write," and "read."
| Permission | Access | What it allows on GitHub | Use stated in Anthropic's docs |
|---|---|---|---|
| Contents | Read and write | Read and write files, branches, and commits | Cloning repositories and pushing branches |
| Workflows | Read and write | Modify files in .github/workflows/ | Pull requests from Claude Tag that fix workflow files |
| Actions | Read and write | View workflow runs, logs, and artifacts; re-run them, and more | Reading CI results. In Claude Tag, also re-running and canceling, triggering workflow_dispatch, deleting runs, logs, and artifacts, and enabling and disabling workflows |
| Repository creation | Read and write | Create and fork repositories in the organization. The app automatically gets access to repositories it creates | No stated use found |
| Repository hooksShown as Webhooks in the UI | Read and write | Create and modify repository webhooks | Plugin marketplace auto-sync |
| Pull requests | Read and write | Create and comment on pull requests | Creating pull requests and posting review comments |
| Issues | Read and write | Create and comment on issues | Replying when mentioned in an issue |
| Checks | Read and write | Create and update check runs | Check runs with Code Review results |
| Discussions | Read and write | Read and write Discussions | For future features (GitHub Actions security doc) |
| Administration | Read | View repository settings (write access would allow changing settings or deleting repositories) | No stated use found |
| MembersOrganization permission | Read | View the organization's members and teams | Checking the connecting user's role in the organization during setup |
| StatusesCommit statuses | Read | View commit statuses (CI pass or fail) | Reading CI that reports results as statuses rather than check runs |
| Dependabot alerts | Read | View Dependabot alerts | No stated use found |
| Merge queues | Read | View merge queues | No stated use found |
| Metadata | Read | Basic repository information | Required by GitHub for every app |
Permissions and access levels are from the list in Claude Code GitHub Actions. What each one allows on GitHub is summarized from Permissions required for GitHub Apps and Choosing permissions for a GitHub App. Uses are from the sources in the previous section and Manage plugins for your organization, except the use of Discussions, which is from security.md in claude-code-action (all checked November 14, 2026). "No stated use found" means the Anthropic documents we checked don't mention one.
There are three things to watch for when reading the list. First, a permission with the same name becomes much more consequential when it changes from read to read and write. Anthropic's example is Actions: once it goes from read to write, the app can re-run workflows instead of only viewing their results. Second, Repository creation lets the app create new repositories in your organization, and according to GitHub, the app automatically gets access to the repositories it creates. Even if you've limited its scope with "Only select repositories," repositories the app creates itself are included. Third, Claude's list grants Administration as read only, so the app can't change settings or delete repositories.
Earlier emails of the same kind (user reports, unofficial)
- February to March 2026: Checks changed from read to read and write (claude-code-action Issue #1041)
- May 2026: Members read and Webhooks read and write (GitHub Community discussion)
- November 2026: Repository creation write (comments on November 6 and 13 in the same discussion)
All dates and details come from user posts. Webhooks, however, is explained in Claude's support article as being for plugin auto-sync (section 1). To see what will be added in your own organization, check the list shown on the approval page. Every permission reported so far is included in Anthropic's list in the table above.
6. Should you approve? A decision for each feature you use
You use Code ReviewIt posts results as check runs, so it uses Checks write access. As the review feature grows, it may need new permissions.
Consider approvingYou hand off work from Slack with Claude TagIf Git providers in Claude's admin settings shows "Needs permissions," an approval is pending. "Review permissions" takes you to GitHub's approval page.
Consider approvingYou auto-sync organization plugins from GitHubIt creates a webhook on the repository, so it needs Webhooks (Repository hooks) read and write. Claude's support article also says organizations that installed the app before this permission was added will see "Claude is requesting updated permissions" and need to approve it.
Consider approvingYou use auto-fix for pull requests in cloud sessionsIt uses Actions and Statuses to read CI results.
Consider approvingYou only use Claude Code GitHub ActionsIt uses three permissions: Contents, Issues, and Pull requests. It doesn't use the new permissions, so there's little reason to rush. If you don't want to grant broad permissions, switch to your own app (steps below).
Fine to waitYou only read repositories through the GitHub integration in claude.aiThis is for reading files, not a feature that uses the additional permissions.
Fine to wait
"Consider approving" means the feature is likely to need the new permissions. The support article says Webhooks is for plugin auto-sync, but there is no dated changelog of which permissions were added when (checked November 14, 2026).
If you're unsure, the quickest approach is to look up each additional permission on the approval page in the table in section 5 and see whether it matches a use for a feature you rely on. If the request includes a powerful write permission with no stated use (Repository creation, for example) and you don't use a feature that needs it, you can also leave it pending and wait.
How to approve
- On GitHub, open your organization's Settings and select GitHub Apps under "Third-party Access."
- Click Configure next to Claude (developer: anthropics). The approval link in the email also points to a page within this app's settings.
- Read the list of additional permissions requested and compare it with the table in section 5.
- To accept, click the approve button. To decline, close the page without doing anything (the current permissions stay).
Narrow the scope with Only select repositories
Under "Repository access" on the same Configure page, choosing Only select repositories instead of All repositories limits Claude to the repositories you pick. You can't change the kinds of permissions, but you can narrow where they apply. As noted above, the one exception is that the app automatically has access to repositories it creates itself. For a worked example of starting with a single repository, see Setting up Claude Code cloud sessions securely.
If you want to undo an approval
GitHub has no way to remove approved permissions one at a time. You have three options.
- Suspend
Suspend on the Configure page blocks the app's access to the organization's resources while keeping it installed. Unsuspend restores it.
- Uninstall
Uninstall removes the app. Other features such as Code Review and Claude Tag stop working too. If you reinstall it, you accept the entire permission list as it stands at that point (users also report that reinstalling brings up the same permissions all at once).
- Your own app
If you only use Claude Code GitHub Actions, you can create and use your own GitHub App with only Contents, Issues, and Pull requests. Code Review and auto-fix in cloud sessions, however, require the official app.
Suspend and Uninstall are from Reviewing and modifying installed GitHub Apps; using your own app is from Claude Code GitHub Actions and setup.md in claude-code-action (checked November 14, 2026).
If you only use GitHub Actions: switching to your own app
- Create a new GitHub App in your organization and limit its repository permissions to read and write on Contents, Issues, and Pull requests (steps in setup.md in claude-code-action).
- Store the app's ID and private key as Actions secrets (
APP_IDandAPP_PRIVATE_KEY), useactions/create-github-app-tokenin your workflow to generate a token for that app, and pass it togithub_token. - After confirming that no other feature relies on Claude's official app, remove the official app.
You still need a secret for your Claude API key or OAuth token, separate from the GitHub App.
7. For organization admins: who can approve, and where to see the record
Only the owner of the account the app is installed on can approve. For an organization, that means the organization owners (Organization owner), and the email goes to each owner. The person who first connects Claude Tag must be an owner of the GitHub organization and also an Owner of the Claude organization.
GitHub's documentation names owners as the people who approve. Claude's support article (Manage plugins for your organization) says the Webhooks approval is done by a "repository or organization admin."
You can check later whether the app's permissions were updated in the organization's audit log. Only organization owners can view the audit log.
- Open the organization's Settings, and under "Archive" in the sidebar, choose Logs, then Audit log.
- Enter
action:integration_installation.version_updatedin the search box. GitHub describes this event as "Permissions for a GitHub App were updated." - To find repositories added to or removed from the installation, search for
integration_installation.repositories_addedandrepositories_removed; for suspensions of the app, search forintegration_installation.suspend.
Sources: Reviewing the audit log for your organization and Audit log events for your organization (GitHub Docs, checked November 14, 2026).
What your organization should decide in advance
You may keep getting this email. Writing down in one document which Claude features you use, who approves, and whom to consult when a powerful write permission (Contents, Workflows, Actions, Repository creation, Webhooks) is added makes each decision faster.
Summary
- "Claude is requesting updated permissions" is a notification GitHub sends to organization owners when Claude, Anthropic's GitHub App, adds permissions.
- To check that it's real, open Claude (developer: anthropics) from GitHub Apps in your organization's Settings, not from the link in the email.
- If you don't approve, the app keeps its current permissions. Features that use the new permissions may not work. You can't approve only some of the permissions.
- The app is shared by GitHub Actions, Code Review, Claude Tag, plugin sync, and more, so its list includes permissions for features you don't use.
- If you use features that run on Anthropic's side, such as Code Review, consider approving; if you only use GitHub Actions, you can wait or use your own app.
- You can narrow the scope with Only select repositories. Permission updates are recorded in the audit log as
integration_installation.version_updated.
FAQ
Q. Is the "Claude is requesting updated permissions" email a scam?
The real email is a notification GitHub sends automatically when a GitHub App's developer adds permissions. It could still be a fake, though, so don't click the link in the email. Instead, go to GitHub Apps in your organization's Settings on GitHub, click Configure next to Claude (developer: anthropics), and check whether the same request appears there.
Q. Will Claude stop working if I don't approve?
No. According to GitHub, if you don't approve, the app keeps working with its current permissions. Features that use the new permissions, however, may not work as expected.
Q. Can I approve only some of the permissions?
No. The Claude Code documentation says GitHub doesn't allow partial approval. To narrow the scope, limit the repositories Claude can access with Only select repositories, or, if you only use GitHub Actions, use your own app with narrower permissions.
Q. Who can approve?
The owner of the account the app is installed on. For an organization, that's the organization owners, and the email goes to them. You can see a record of the app's permission updates by searching the organization's audit log for integration_installation.version_updated.
Q. Why does Claude keep asking for permissions?
Because one app is shared by GitHub Actions, Code Review, Claude Tag, plugin sync, and more, and the permission list changes each time a feature is added. Anthropic says the permission list can change before the features that use it ship.
Update history
- November 14, 2026Published.
Sources
- Approving updated permissions for a GitHub App (GitHub Docs)
- Modifying a GitHub App registration (GitHub Docs)
- Reviewing and modifying installed GitHub Apps (GitHub Docs)
- Choosing permissions for a GitHub App (GitHub Docs)
- Permissions required for GitHub Apps (GitHub Docs)
- Audit log events for your organization (GitHub Docs)
- Claude Code GitHub Actions (Anthropic)
- Claude Code with GitHub Enterprise Server (Anthropic)
- Code Review (Anthropic)
- Configure GitHub access (Claude Tag, Anthropic)
- Manage plugins for your organization (Claude support article)
- Sync your organization's plugins from a repository (Anthropic)
- security.md in claude-code-action (Anthropic; used only for the use of Discussions)
- GitHub App permission updates should allow per-scope approve/reject (GitHub Community, user discussion)
- Claude GitHub app requesting updated permissions (claude-code-action issue, user report)