From edd410d8e85c7957961a090bcc9afeaba77f7f4a Mon Sep 17 00:00:00 2001 From: John B Joseph <223714458+Johnbjoseph-cybersec@users.noreply.github.com> Date: Thu, 12 Nov 2026 12:28:49 +0530 Subject: [PATCH 1/2] docs: correct fine-grained PAT organization controls in policies-and-governance.md --- docs/policies-and-governance.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/policies-and-governance.md b/docs/policies-and-governance.md index d7f52212ab..447d59ec2a 100644 --- a/docs/policies-and-governance.md +++ b/docs/policies-and-governance.md @@ -120,9 +120,9 @@ Access is always constrained by GitHub's public API permission model and the aut * **Limitations:** PATs do not adhere to OAuth App policies and GitHub App installation controls. They are user-scoped and not recommended for production automation. * **Organization controls:** * Classic PATs: Can be completely disabled organization-wide - * Fine-grained PATs: Cannot be disabled but require explicit approval for organization access + * Fine-grained PATs: Can also be blocked from organization resources, set separately on the Fine-grained tokens tab. By default, tokens created by organization members also need an organization owner's approval before it can access organization resources; owners can turn this approval requirement off ([PAT policies](https://docs.github.com/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization#enforcing-an-approval-policy-for-fine-grained-personal-access-tokens)) -> **Recommendation:** We recommend using fine-grained PATs over classic tokens. Classic tokens have broader scopes and can be disabled in organization settings. +> **Recommendation:** We recommend using fine-grained PATs over classic tokens. Classic tokens have broader scopes. Both token types can be blocked from organization resources in organization settings. ### 4. SSO Enforcement (overlay control) From 47767af386f0ebbd82d39b4ca015f8d06aeeae25 Mon Sep 17 00:00:00 2001 From: John B Joseph Date: Tue, 17 Nov 2026 09:46:43 +0530 Subject: [PATCH 2/2] docs: note the organization owner exception for fine-grained PAT approval Tokens created by organization owners do not need approval, per GitHub's personal access token policy docs. Co-Authored-By: Claude Opus 5.5 --- docs/policies-and-governance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/policies-and-governance.md b/docs/policies-and-governance.md index 447d59ec2a..0485e60036 100644 --- a/docs/policies-and-governance.md +++ b/docs/policies-and-governance.md @@ -120,7 +120,7 @@ Access is always constrained by GitHub's public API permission model and the aut * **Limitations:** PATs do not adhere to OAuth App policies and GitHub App installation controls. They are user-scoped and not recommended for production automation. * **Organization controls:** * Classic PATs: Can be completely disabled organization-wide - * Fine-grained PATs: Can also be blocked from organization resources, set separately on the Fine-grained tokens tab. By default, tokens created by organization members also need an organization owner's approval before it can access organization resources; owners can turn this approval requirement off ([PAT policies](https://docs.github.com/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization#enforcing-an-approval-policy-for-fine-grained-personal-access-tokens)) + * Fine-grained PATs: Can also be blocked from organization resources, set separately on the Fine-grained tokens tab. By default, a fine-grained PAT needs an organization owner's approval before it can access organization resources, except tokens created by organization owners, which need no approval; owners can turn this approval requirement off ([PAT policies](https://docs.github.com/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization#enforcing-an-approval-policy-for-fine-grained-personal-access-tokens)) > **Recommendation:** We recommend using fine-grained PATs over classic tokens. Classic tokens have broader scopes. Both token types can be blocked from organization resources in organization settings.