Learn how to configure source control repository permissions using GitHub

Learn how to configure source control repository permissions using GitHub

GitHub provides a range of repository permissions tailored to different plans, including personal accounts, organizations, teams, and enterprise environments. Below is a breakdown of how repository permissions are configured across various GitHub tiers.

1. Repo Permissions in GitHub Free for Personal Accounts

In GitHub Free for personal accounts, the following permissions apply:

• Collaborators: Full control over the repository, including commit rights, merging, and setting branches.

• Read: View-only access to the repository (issues, pull requests, commits).

• Write: Can push changes, create branches, and submit pull requests.

• Admin: Full repository access, including administration of settings, collaborators, and repository-level access.

2. Repo Permissions in GitHub Pro

In GitHub Pro, the permissions remain largely the same as GitHub Free for personal accounts but may include additional collaboration features and access to advanced analytics.

• Collaborators: Full control over the repository, including commit rights, merging, and managing settings.

• Read: View-only access to the repository.

• Write: Can push changes, create branches, and submit pull requests.

• Admin: Similar to Collaborators, but can also manage repository-level configurations.

3. Repo Permissions in GitHub Free for Organizations

In GitHub Free for organizations, permissions are managed at the repository and organizational level:

• Admin: Full control over repository settings, including managing collaborators, teams, and repository visibility.

• Write: Ability to push changes, create branches, submit pull requests, and merge.

• Read: View-only access.

• Minimal: Restricted access to view-only functionality.

4. Repo Permissions in GitHub Team

In GitHub Team, permissions allow finer granularity:

• Admin: Full control of the repository, including managing collaborators, permissions, and team access.

• Write: Can push changes, submit pull requests, and merge.

• Read: View-only access to the repository.

• Custom: Teams can be assigned specific permissions (e.g., issues, pull requests).

5. Repo Permissions in GitHub Enterprise Cloud

In GitHub Enterprise Cloud, organizations have the most customizable permissions:

• Owner: Full control over repository settings, including organization management and user permissions.

• Admin: Similar to Owner, but limited to a specific repository.

• Write: Can push changes, create branches, and submit pull requests.

• Read: View-only access to repositories.

• Restricted: Allows viewing and limited access to specific sections such as issues or pull requests.

Configuring Permissions:

1. Access Settings: Navigate to Settings > Collaborators & teams for repository-level permissions.

2. Manage Collaborators and Teams: Assign specific roles (Admin, Write, Read) to individual users or teams.

3. Custom Permissions: Define custom permissions for specific roles or repositories, especially in organizations or enterprise environments.

Summary of Repository Permissions Across GitHub Plans

This flexibility allows organizations and individuals to manage repository access according to the level of collaboration, development, and administrative control required.