Manage GitHub Project Access
Set project visibility and project roles independently from repository access. Access to a project does not automatically grant permission to read all issues from private repositories inside it.
Step-by-step guide
Check access and scope
Project administration permission is needed to manage access. Organization-level and user-level projects use different collaboration scopes.
Define audience actions
Identify the audience and the actions each person needs.
Review visibility and base role
Review project visibility and organization base role.
- Worked example: A cross-team release project may include private security work that some stakeholders cannot open. Provide an approved summary rather than granting broad repository access solely to make a dashboard look complete.
Grant specific access
Grant specific team or collaborator roles where appropriate.
Inspect private and draft items
Inspect private-repository items and external references.
Test the reader view
Test the view as a reader with the intended repository permissions.
Verify the result
Readers see the intended planning information without unexpected editing powers or exposed confidential drafts.
Common mistakes
Check the handoff edge case
A permissive organization base role can grant broader project editing than intended. Review base access as well as individual invitations.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.