GitHub repository roles for an organization
Documents repository role levels, granular permissions for read, triage, write, maintain, and admin access, base permissions, organization settings, and action-specific access limits.
What this source can teach
Use this source to inspect a concrete implementation and the decisions visible in its context.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Permission denied state | Choose permission denied state when the primary cause is missing authorization, role membership, share grant, license entitlement, approval, or organization policy. | The denial is durable until the permission, account, role, policy, or request state changes. | GitHub documents role-based repository permissions and action-specific access boundaries. |
| Permission recovery | Choose permission recovery when the interface needs to guide users through request, approval, switch-account, policy, fallback, or retry-after-grant steps after a permission denial. | The recovery workflow opens from a known permission denial and keeps the original object or action attached when safe to reveal. | GitHub documents role-based repository boundaries that support action-specific role upgrade and admin-contact recovery paths. |
| Permission sharing | Choose permission sharing when users manage durable access grants, role assignments, group permissions, effective access, inheritance, anonymous access, or revocation for a protected resource. | Opening the permission sharing surface loads direct grants, inherited grants, group or team grants, anonymous access, service credentials, and owner or admin constraints before edits are saved. | GitHub documents repository role levels and action-specific permission differences for Read, Triage, Write, Maintain, and Admin. |
Comparisons supported by this source
- Permission denied state vs error state vs empty state vs disabled button no explanation
GitHub repository roles document action-specific permission levels and role boundaries.
- Permission recovery vs permission denied state vs session timeout warning vs retry
GitHub repository roles document action-specific role boundaries for role upgrade and admin-contact recovery.
- Permission sharing vs share dialog vs invite user vs permission recovery
GitHub documents repository role levels and action-specific permission differences such as access management being admin-only.
Evidence Role
This source is treated as product-example evidence. Its value comes from the specific claims and setting described above.
Publisher: GitHub Docs. Last checked: .