📣 New: See how repository access is granted for organization members

[moraesc]

Organization admins can now see exactly how each member's repository access is granted - whether through organization membership, a team, or a direct assignment - directly from the member's repository list on your organization's People page.

Previously, you could see which repositories a member had access to, but not why. You'd have to drill into each repository individually to understand the source of their access. Now that context is surfaced inline, you can audit and understand your organization's access patterns immediately.

What's changed

• The repository list on /orgs/{ORG}/people/{USERNAME} now includes a compact summary of how access was granted for each repository
• Redundant "Has access to X repositories" messaging has been removed for a cleaner layout

Who this is for

This is an organization page for admins, so only organization admins will see the source of a member’s access details when viewing a member's repository list.

Why it matters

For open source projects with large contributor bases, understanding the source of repository access is important for keeping permissions clean and intentional. This makes it easier to spot access that may have been granted in unexpected ways, without having to dig through team and role settings for each repository individually.

If you have any questions or feedback, let us know in the comments below. 👇