GitHub members, teams, and access

Open Workspace > Integrations, select the connected GitHub account, then choose People & access. You need workspace Admin or Owner access and the Platform feature.

These lists describe captured GitHub access. Check the connection's capture time and any permission warning before using them for an access review. Change membership or permissions on GitHub, then sync the connection to check the updated evidence.

Find membersCopy Anchor Link

1. Choose Members and enter a GitHub login in Search members.
2. Use Member role to show Admins, Members, or All roles. These are GitHub roles, separate from Sorena workspace roles.
3. Use Two-factor authentication state to find 2FA disabled or 2FA enabled. Two-factor authentication (2FA) adds a second check when signing in.
4. Use Outside collaborator state to separate Outside collaborators, who have access without organization membership, from Organization members.
5. Choose Sort members by Login or Role, then choose an ascending or descending Sort order. Review the other result pages when needed.

Read each row's role, two-factor authentication, and access type together. Clear filters restores the broader member list and default ordering. A list with no matching members does not prove the organization has no members.

The summary also shows pending personal access token (PAT) requests, blocked users, and self-hosted runners. These are captured counts; review requests and manage those resources on GitHub.

Find teamsCopy Anchor Link

Choose Teams, then search by team slug, the short team name used by GitHub. Sort teams offers Team slug, Member count, and Repository count, with an ascending or descending Sort order.

Review each team's privacy, member count, and repository count. Move through the result pages to review the full filtered list. Choose Clear filters to clear the search and restore the default ordering.

Review repository permissionsCopy Anchor Link

Choose Repository access to inspect captured access grants. A grant records access assigned to a user or team. The Principal is the user or team receiving that access.

1. Use Search repository access for a broad search across repositories, teams, and users.
2. Choose Principal kind to show Direct user access, Team-derived access, or both. Team-derived access comes through team membership; a direct user grant is assigned to that user.
3. Choose Effective permission to narrow by Pull, Triage, Push, Maintain, or Admin. These range from reading a repository to managing it; use the displayed permission when reviewing the grant.
4. Enter the complete owner and repository name in Repository for an exact match. Enter the exact team slug or GitHub user login in Principal when reviewing a particular recipient.
5. Sort by Repository, Principal, or Permission, choose the order, and review the other result pages.

Read Access path alongside the permission. It shows the captured team source or repository role and, where available, whether a direct user is an outside collaborator or organization member. A missing source or membership value means that detail is unavailable.

Choose Clear filters to remove the active criteria. If the full list is still empty, Sorena has no captured grants to show. If the page warns that people evidence needs GitHub permission, confirmed rows may be visible while membership or team coverage remains incomplete. Follow GitHub access guidance before treating the list as complete.

Screenshots show a demo workspace.