REST API: expose org-level classic PAT policy setting (disable classic personal access tokens)

[corinnakollegger]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

API

Body

What problem does this solve?

GitHub allows organization admins to disable classic personal access tokens
org-wide via the UI (Settings → Personal access tokens → "Allow access via
personal access tokens (classic)"). However, this setting is not exposed via
the public REST API - it is absent from PATCH /orgs/{org}.

This makes it impossible to manage this security-critical setting as code.
Organizations that manage GitHub configuration programmatically (via Terraform,
Kubernetes operators, or CI workflows) cannot enforce or drift-correct this toggle.

Current workaround

None. The setting must be applied manually through the GitHub UI by an org admin.

Proposed solution

Add a field to PATCH /orgs/{org}, for example:

members_can_create_classic_personal_access_tokens: false

This follows the same pattern as existing fields like
members_can_create_public_repositories.

Related discussions

• API to get list of legacy personal access token (PAT) for users in the organization #61490 — API to list legacy PATs for org users (related gap)

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐