Configure GitHub access changedclaude-tag/admins/configure-github
Nearest release: v2.1.240, published 3 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+7added
Lines−8removed
From line
17
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits19to this page, all time
The whole hunk
from line 17, old and new numbered
/
from line 17
1717## Link your GitHub organization
1818
1919<Note>
20 The person who completes the link must be both an **owner of the GitHub organization** and an **Admin in your Claude organization**. If you aren't a GitHub organization owner, use **Copy message** under **Not a GitHub account owner?** on the GitHub settings page to send the link to someone who is.
20 The person who completes the link must be both an **owner of the GitHub organization** and an **Owner in your Claude organization**. If you aren't a GitHub organization owner, use **Copy message** under **Not a GitHub account owner?** on the GitHub settings page to send the link to someone who is.
2121</Note>
2222
2323<Steps>
from line 68
6868
6969Repository grants apply to new threads. After changing the **Repositories** tab, start a fresh thread in the channel and name the repository in the first message.
7070
71The message "GitHub Actions writes are not permitted for this session type." is a different `403`. It says nothing about repository access; see [What Claude can do with GitHub Actions](#what-claude-can-do-with-github-actions).
71A `403` that names a GitHub Actions operation, such as "repository\_dispatch is not permitted for this session type.", is a different error. It says nothing about repository access; see [What Claude can do with GitHub Actions](#what-claude-can-do-with-github-actions).
7272
7373## How granted repositories reach a session
7474
from line 101
101101Claude can:
102102
103103* Read workflow runs, jobs, logs, and artifacts, so it follows a pull request's CI and reports the result
104* Re-run a workflow run or its failed jobs, and cancel a run in progress
105* Trigger `push` and `pull_request` workflows by pushing a branch or opening a pull request, the same way any other author does. To let Claude start automation on demand, put the workflow behind one of these triggers instead of `workflow_dispatch`
104* Re-run a workflow run or its failed jobs, cancel a run in progress, and dispatch a `workflow_dispatch` workflow
105* Delete runs, logs, or artifacts, and enable or disable a workflow
106* Trigger `push` and `pull_request` workflows by pushing a branch or opening a pull request, the same way any other author does
106107* Edit files under `.github/workflows/` and open a pull request with the change, like any other file
107108
108109Claude can't:
109110
110* Dispatch a workflow (`workflow_dispatch` or `repository_dispatch`)
111* Send a `repository_dispatch` event
111112* Approve a workflow run that's waiting on approval, or its pending deployments
112* Delete runs, logs, or artifacts
113* Enable or disable a workflow
114113
115A request for any of those is refused with a `403`. A `repository_dispatch` request returns "repository\_dispatch is not permitted for this session type." The others return "GitHub Actions writes are not permitted for this session type." Dispatching a workflow or approving a held run starts new code running with the repository's Actions secrets, so it needs a person; do it from the repository's **Actions** tab on github.com.
114A request for either is refused with a `403`; a `repository_dispatch` request returns "repository\_dispatch is not permitted for this session type." Approving a held run or a pending deployment releases a checkpoint GitHub inserted for a person, so do it from the repository's **Actions** tab on github.com.
116115
117116## Scheduled work uses the same connection
118117
No line in this hunk matches that.