You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -161,7 +161,11 @@ If a policy is enabled for an enterprise, the policy can be selectively disabled
161
161
162
162
In the "Workflow permissions" section, you can set the **default** permissions granted to the `GITHUB_TOKEN`.
163
163
164
-
***Read and write permissions:** By default, `GITHUB_TOKEN` has read and write access for all scopes.
164
+
***Read and write permissions:** The default permissions for the `GITHUB_TOKEN` depend on when the enterprise or organization was created:
165
+
166
+
***Created on or after February 2, 2023** – Defaults to **read-only** access for all scopes.
167
+
***Created before February 2, 2023** – Defaults to **read and write** access for all scopes.
168
+
165
169
***Read repository contents and packages permissions:** By default, `GITHUB_TOKEN` has only read access for the `contents` and `packages` scopes. The more permissive setting cannot be chosen as the default for individual organizations or repositories.
166
170
167
171
Anyone with write access to a repository can still modify the permissions granted to the `GITHUB_TOKEN` for a specific workflow, by editing the `permissions` key in the workflow file.
0 commit comments