> ## Documentation Index > Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt > Use this file to discover all available pages before exploring further. # Demo Describe Members Teams and Roles in a GitHub Organization > Explains GitHub organization roles, members, outside collaborators, teams, and repository permissions and how to manage access and settings via the GitHub user interface. In this lesson we'll explain how people are organized and granted access inside a GitHub organization. You'll learn how Owners, Members, Outside Collaborators, and Teams relate to repositories and permissions, and where to manage these settings in the GitHub UI. ## Viewing organization people To inspect who belongs to an organization, open the organization’s People tab. Members are grouped into Owners and Members; Outside Collaborators are listed separately. Use the membership-type filters to locate Owners, Members, or Outside Collaborators quickly. The image shows a GitHub organization page with a list of members, their roles, and two-factor authentication status. The interface is dark-themed and includes an "Invite member" button. ## Organization roles: Owners Owners have full administrative control across the organization: they manage teams, member settings, billing, policies, and can delete the organization. The user who creates the organization is an Owner by default. Limit Owner assignments to trusted administrators. The image shows a GitHub organization page titled "Pixelcraft-Studio-kk," displaying a member list where one user, marked as an owner with two-factor authentication enabled, is present. ## Members: default and effective permissions Organization Members receive the organization’s default repository permission (commonly `Read`), which you can configure. A member’s effective permissions may be raised or restricted by: * Team memberships (teams can grant broader repo access). * Repository-level collaborator settings (Manage access / Collaborators & teams). * Organization or repository policy restrictions. Open a member’s profile and select **Manage access** to review the repositories they can access and their permission levels. The image shows a GitHub organization page for "Pixelcraft-Studio-kk," displaying a member profile with access details and security settings. ## Repository-level permissions Repository permissions are managed from the repository **Settings → Collaborators & teams** (or **Manage access**). There you can add or remove collaborators, change roles, and create or assign custom roles when available. The image shows a GitHub repository access settings page for "Pixelcraft-Studio-kk/block-buster," indicating specific user permissions for reading, writing, and admin access. The user has active read access, but no explicit write or admin permissions. The image shows a GitHub repository settings page focused on managing access, with options for direct and organization access, and a role selection dropdown. Various user permissions like "Read," "Triage," and "Write" are displayed, along with an option to create custom roles. Summary of common repository roles: | Role | Typical use | Effect | | -------- | ------------------ | ----------------------------------------------------------- | | `Read` | View code & issues | Clone and read-only access | | `Triage` | Manage issues/PRs | Issue/PR management without write to code | | `Write` | Contribute code | Push changes and merge PRs (depending on branch protection) | | `Admin` | Full repo control | Manage settings, collaborators, webhooks | For more details, see the official GitHub documentation on repository permissions: [Managing repository access](https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories). ## Outside collaborators Outside collaborators are users who have access to one or more repositories but are not organization Members. This is useful for contractors, temporary contributors, or external partners. From the People tab you can view the repos they can access, invite them to become full organization Members, or remove their access. The image shows a GitHub organization page for "Pixelcraft-Studio-kk," with a user named "sidd-harth-1" listed as an outside collaborator who has access to one repository. There are options to invite the user to the organization or remove access. Use outside collaborators to grant repository-scoped access without making someone a full organization Member. Invite them as Members only when they need broader organization-level privileges. ## Teams: group-based access and notifications Teams let you group Members to manage repository access, notifications, and mentions efficiently. Typical workflows: * Give `UI-Team` write access to front-end repositories. * Give `Backend-Team` admin or write access to API repositories. * Mention a team in an issue or PR to notify all team members with a single handle. To create a team, supply a name, description, visibility (visible or secret), and notification settings. Teams can also be organized into parent/child hierarchies. The image shows a GitHub interface for creating a new team, with fields for team name, description, visibility, and notifications settings. The team is named "UI-Team" with a description related to UI repositories. When you create a team, the creator is added as a team maintainer by default. You can invite additional members and assign other maintainers to manage the team. This image shows a GitHub team page for "UI-Team" under the organization "Pixelcraft-Studio-kk," listing a member named "sid-gh900." The interface includes options for managing team members and roles. Teams support features such as flexible repository access scopes, team join requests, and team mentions. The image is a GitHub interface overview for team features, highlighting flexible repository access, team requests, and team mentions. The page includes options to add a team and learn more. Once a team and its members are in place, you can mention the team in issues, pull requests, and comments to notify everyone in the group at once. Use the team handle format, for example: `@org/UI-Team`. The image shows a GitHub page titled "Seamless communication with teams," highlighting features for team collaboration, and includes a section for managing teams, with one team called "UI-Team" selected. Grant Owner status sparingly. Prefer teams and repository-level roles to minimize blast radius and adhere to the principle of least privilege. ## Quick reference * Owners = full organization control — limit assignments. * Members = organization-scoped users with a default repo permission. * Outside collaborators = repo-scoped access without organization membership. * Teams = group-based access, notifications, and easier management. For additional reading and step-by-step UI guidance, visit: * [GitHub Organizations documentation](https://docs.github.com/en/organizations) * [Manage access to your repositories](https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)