Improved organization permissions
Organizations have always been the best way for teams to work together and collaborate on code. We’re happy to announce major improvements to GitHub organization permissions. These improvements include new…
Organizations have always been the best way for teams to work together and collaborate on code. We’re happy to announce major improvements to GitHub organization permissions. These improvements include new customizable member privileges, fine-grained team permissions, and more open communication.
The improved permissions system gives your organization the flexibility to work the way you want. Here are just a few highlights:
- (Opt-in) Members can view and mention all teams, even when they’re not on those teams.
- (Opt-in) Members can create repositories without help from an owner.
- Members can create new teams to self-organize with the people they work with.
- Owners can give just the right amount of access to contractors and interns by adding them to repositories without giving them the privileges of organization members.
- And many more! Learn about GitHub’s improved organization permissions.
All of these new features give your organization the ability to work together seamlessly without everyone needing to be an owner.
Once these features launch, organization owners will be able to turn on new permissions as needed. Simply opt-in when you’re ready.
Coming soon
In the next few months, every organization on GitHub.com will have the improved permissions system.
Written by
Related posts

From MCP to multi-agents: The top 10 new open source AI projects on GitHub right now and why they matter
Get insights on the latest trends from GitHub experts while catching up on these exciting new projects.

Racing into 2025 with new GitHub Innovation Graph data
Discover the latest trends and insights on public software development activity on GitHub with the quarterly release of data for the Innovation Graph, updated through December 2024.

GitHub Availability Report: March 2025
In March, we experienced one incident that resulted in degraded performance across GitHub services.