Permissions and roles in GitHub — quick notes
GitHub permissions — quick notes
| Role | Purpose |
|---|---|
| Read | Pull, view/discuss, open issues |
| Triage | Manage issues/discussions/PRs without write |
| Write | Active contribution, subject to branch/ruleset controls |
| Maintain | Manage repo without sensitive/destructive actions |
| Admin | Full repository access |
- Prefer a team for reusable member access; direct grants remain supported. Child teams inherit parent permissions.
- Outside collaborator = repository-scoped nonmember; cannot join teams and gets no base permission.
- Roles grant baseline capabilities; branch protection and rulesets add restrictions, requirements, and bypass controls.
Sources: https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/az-400 · https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization · https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams · https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators/adding-outside-collaborators-to-repositories-in-your-organization · https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/setting-base-permissions-for-an-organization · https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches · https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets · https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository