I am in multiple teams in one org, each with different levels of access to the same repository. What level of access do I end up with?

[clairep94]

🏷️ Discussion Type

Question

Body

I'm a member of an open source organisation, and am trying to work out what level of access I have to a target repo, which the organisation owns

Within the org, I have been assigned to two teams

Team A has 'maintain' access to the target repo
Team B has 'triage' access to the target repo

I cannot locate anywhere to view my individual user's level of access for this repo. Is it possible to surface this somewhere?
What access do I end up with in this scenario? The highest level ('maintain')?

[bideshbiswas]

Yes, you will end up with 'maintain' access. When you belong to multiple teams with different access levels to the same repository, GitHub's permission model resolves overlapping permissions by always granting the highest (most permissive) level of access. Since 'maintain' is higher than 'triage', that is the role you inherit.
Unfortunately, there isn't a dedicated page where standard organization members can view their computed individual access level for a specific repository. Only Organization Owners have access to the specific settings page that breaks down exactly how a user inherited their permissions.
However, the quickest workaround to verify your access is to navigate to the target repository and look for the Settings tab at the top. Since 'triage', 'read', and 'write' roles cannot access repository settings, seeing that tab confirms your 'maintain' status.

[IsaacPolignac]

You will receive the highest (most permissive) level of access granted across all the teams you belong to.
GitHub always resolves overlapping permissions by favoring the most privileged tier:
Read < Triage < Write < Maintain < Admin
For example, if Team A grants you Read access and Team B grants you Write access to the same repository, your effective permission on that repository will be Write. If direct collaborator access is also granted to your account individually, the highest permission between your direct access and team access applies.

[aryamanxsingha]

Because you belong to both Team A ('maintain') and Team B ('triage'), your 'maintain' access overrides the lower 'triage' access. You effectively have 'maintain' access to the target repository.

Viewing Your Access Level
There is currently no native "My Permissions" view on a GitHub repository that explicitly states your individual access tier. Whether you can view this information depends on your privileges:

Repository Admins / Org Owners: Can navigate to the repository's Settings > Collaborators and teams (or Manage access) to view a complete list of users and their calculated effective roles.

Maintain, Write, Triage, or Read Users: Cannot view the repository's access management pages. To verify your exact access level, you must either:
-Deduce it via UI capabilities: With 'maintain' access, you will see options to manage issues and pull requests, push code, and edit select repository settings (like branch protections). You will noticeably lack the ability to delete the repository, transfer ownership, or manage other users' access.
-Ask an Admin: Request an Organization Owner or Repository Admin to check your effective permissions for you in the repository's settings.