User accounts and organization accounts use different permissions models for the repositories owned by the account.

User accounts

User accounts only have two permission levels, the account owner and collaborators.

Owner

This user has full control of the account and the private repositories directly owned by the account. There is only one owner of a user account's repositories, this cannot be shared with another user.

Collaborator

Has push/pull access to the repositories they have been granted collaborator access. See the "Write Access Teams" and "Read Access Teams" permissions below for more details.

Organization accounts

There are four levels of access available to organization account teams. Each level includes the permissions of the levels below it. Except for Owners, team members only have access to the team they are in and the repositories assigned to that team.

Owners
Repository Access
  • Full access to all repositories owned by the organization
Team Access
  • Full access to all the teams in the organization
Organization Account Settings
  • Full access to all the organization account settings
  • View and edit billing information
  • Edit organization profile and public members
  • Delete organization account and all its contents
Admin Access Teams
Repository Access
  • Create repositories within the admin team
  • Change settings and delete repositories assigned to the admin team
  • Transfer repositories into the organization account
  • Transfer repositories assigned to the admin team out of the organization account
Team Access
  • Add and remove users from the admin team
  • Cannot add other teams to the repositories they admin
  • Cannot add or remove users from other teams
Organization Account Settings
  • No access

Note: Admin teams don't administer the entire account. For example, you can't add or remove users in different teams.

Write Access Teams
Repository Access
  • Push (write) to the repositories assigned to the team
  • Apply labels, milestones and assign issues
  • Close and re-open issues
  • Edit and delete all commit, pull request and issue comments
  • Merge and close pull requests
Team Access
  • View current team and owners
Organization Account Settings
  • No access
Read Access Teams
Repository Access
  • Pull (read) from the repositories in the team
  • Fork the repositories in the team
  • Send pull requests from forks
  • Open issues
  • Edit and delete commit, pull request and issue comments from the current user
  • Edit wikis
Team Access
  • View current team and owners
Organization Account Settings
  • No access

Warning: There is no team permission that allows access to Issues, but blocks read access to repositories. However, you can create a second repository that contains only Issues, and store your code repository in separate, private repository.