Build what's next on GitHub, the place for anyone from anywhere to build anything.
Join us October 28-29 in San Francisco or online for GitHub Universe, our flagship developer event uniting people, agents, and the world's code.
Updates to organization project permissions add to existing workflows and make new ones possible.
Our latest changes to organization project permissions introduce more possibilities for your organization’s workflow. Collaborate with your team in new ways, expand who you work with, and, if you’d like, publicly communicate your progress across projects to the community.
Sometimes projects aren’t relevant to every organization member. Now you can set permissions for your organization’s projects that specify which members can see or edit a project.
We’re also expanding the ways you can collaborate with others, so you can invite outside collaborators to your projects, too. Bring in external team members like contractors to work with you on certain projects without having to add them directly to your organization—the same way that repository permissions work.
Happy with your permissions the way they are? Permissions for existing project won’t change unless you update their collaboration settings or create a new project using the new permissions options.
Previously, you had to create a repository-level project on a public repository to share a project with the world. Now you can create public projects at the organization level, too. Share your organization’s public roadmap with the world, or set up a project to triage incoming issues that span multiple repositories for a single open source project. We’re excited to see how you use public projects to tell the world what you’re working on.
For more detailed information on how to work with organization project permissions, see the documentation.
