Delegate responsibilities with expanded repository permissions
Administrators of organization-owned repositories can now assign “triage” and “maintain” roles to collaborators and teams.
![](https://github.blog/wp-content/uploads/2019/03/company-twitter.png?resize=1201%2C630)
It’s no surprise that we believe the best software is built together. Users open issues to report bugs or request new features, contributors discuss potential implementations, and maintainers review proposed changes. But as a project and its community grows, ensuring that feedback and decisions are addressed can often be a full-time job on top of the work you’re already doing.
Historically, repository permissions on GitHub were limited to read
, write
, and admin
. The only way to grant additional permissions to individual teams or members was to provide them with full permissions to modify a project’s source code. At Satellite, we launched a public beta of our triage
and maintain
roles to empower administrators to delegate responsibilities to trusted members. Today, these roles are now generally available.
New role details
Triage
The triage
role allows users to more proactively manage projects without the need for write access to the code. These users are able to open and close issues and pull requests, request reviews from developers, and manage project milestones.
Maintain
The maintain
role allows users to manage a repository without access to sensitive or potentially destructive actions. These users are able to create and edit releases, push to protected branches, lock conversations, and manage interaction limits.
Role availability
These new roles are now available to all organizations on the Free, Team, and Enterprise Cloud plans. Organization and repository admins can apply the roles to teams and users in the Collaborators & teams tab of their repository settings page.
Learn more about permissions for organizations
Tags:
Written by
Related posts
![](https://github.blog/wp-content/uploads/2023/10/Collaboration-DarkMode-2.png?resize=400%2C212)
2024 is the biggest global election year in history. What’s at stake for developers?
GitHub is considering what is at stake for our users and platform, how we can take responsible action to support free and fair elections, and how developers contribute to resilient democratic processes.
![](https://github.blog/wp-content/uploads/2023/10/AI-DarkMode-2.png?resize=400%2C212)
GitHub named a Leader in the Gartner first-ever Magic Quadrant for AI Code Assistants
This year, as part of its annual Magic Quadrant series, Gartner published a first-of-its-kind report analyzing the state of play in the AI Code Assistants market–and named GitHub a Leader.
![AI in software development 2024 survey results with colorful graphics and percentages.](https://github.blog/wp-content/uploads/2024/08/ai-survey-header.png?resize=400%2C212)
Survey: The AI wave continues to grow on software development teams
We surveyed 2,000 people on software development teams at enterprises in the U.S., Brazil, India, and Germany about the use, experience, and expectations around generative AI tools in software development.