diff --git a/content/collaborating/create-organization.md b/content/collaborating/create-organization.md index 4ed196c..2ed0e22 100644 --- a/content/collaborating/create-organization.md +++ b/content/collaborating/create-organization.md @@ -100,7 +100,6 @@ Click the green `+ New Team` to create a new team. Define its name, permissions You can choose whether members of the team can only access some repositories explicitly added to the team, or whether they can access all repositories of the organziation. You can also allow members to be able to create new repositories for the organization. If you have allowed repository administrators to grant or remove access for teams (see [Create an Organization](#create-orga) above), they can do so in `Settings > Collaborators` tab of the repository. - If you choose either `Read` or `Write` access, you can additionally define which sections of the repositories (code, issues, pull requests, releases and wiki) the members will have (read or write) access to. On the other hand, `Administrator` access automatically grants read and write access to all sections; this part of the form is therefore hidden in this case. See the section [Access rights](#access-rights) below for details. @@ -138,124 +137,13 @@ Finally, you can choose to leave the organization from here. ## Access rights -The table below gives an overview of the permission system for organizations based on teams: +An overview of the repository permissions in given in the article [Repository Permissions](/collaborating/repo-permissions). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- * Access to specific sections can be restricted by owners. -
Task Other Teams Team "Owners"
Read access Write access Admin access
View, clone and pull team repository * * *
Contribute pull requests
Push to/update contributed pull requests
Push directly to team repository
Merge pull requests
Moderate/delete issues and comments
Force-push/rewrite history (if enabled)
Add/remove collaborators to team repository
Configure team repository settings (enable wiki, issues, PRs, update profile)
Configure branch settings (protect/unprotect, enable force-push)
Edit team repository settings from the Danger Zone (transfer ownership, delete wiki data and repository, and archive repository)
Edit/delete organization
Add/remove team or member
Define access rights of teams
+Members of the "Owners" team can do everything that admins can do. But only owners of the organization can manage the organization, which includes: +- edit/delete the organization, +- add/remove members and teams, +- define access rights of teams, +- edit organization repository settings in the danger zone (i.e. transfer ownership, delete wiki data and repository, and archive repository). -When owners allow members of a team to be able to create new repositories for the organization (see box "Create repositories" in [Teams](#teams) settings), the member who creates the repository will be granted administrator rights for this repository, that is, editing all settings of the repository except those in the `Danger Zone` (transfer ownership, delete wiki data and repository, and archive repository). The member will be added as a collaborator to this repository (see [Invite Collaborators](/collaborating/invite-collaborators) for details). +When owners allow members of a team to be able to create new repositories for the organization (see box "Create repositories" in [Teams](#teams) settings), the member who creates the repository will be added as a collaborator with administrator rights to this repository (see [Invite Collaborators](/collaborating/invite-collaborators) for details). diff --git a/content/collaborating/invite-collaborators.md b/content/collaborating/invite-collaborators.md index 42632f2..8508748 100644 --- a/content/collaborating/invite-collaborators.md +++ b/content/collaborating/invite-collaborators.md @@ -27,7 +27,7 @@ Then navigate to the `Collaborators` tab and search for the user you want to add add-collaborator -Once added, you can define the access rights by clicking on the shield: `Read` (can see but not edit), `Write` (can see and edit) or `Administrator` (can do everything!). This is also where you can remove collaborators. +Once added, you can define the access rights by clicking on the shield: `Read`, `Write` or `Administrator` (see [Repository Permissions](/collaborating/repo-permissions) for details). This is also where you can remove collaborators. diff --git a/content/collaborating/repo-permissions.md b/content/collaborating/repo-permissions.md new file mode 100644 index 0000000..e36e0c7 --- /dev/null +++ b/content/collaborating/repo-permissions.md @@ -0,0 +1,104 @@ +--- +eleventyNavigation: + key: RepoPerm + title: Repository Permissions + parent: Collaborating + order: 50 +--- + +When you invite collaborators to join your repository (see [Invite Collaborators](/collaborating/invite-collaborators)) or when you create teams for your organization (see [Create and Manage an Organization](/collaborating/create-organization)), you have to decide what each collaborator/team is allowed to do. + +There are four permission levels: Read, Write, Administrator and Owner. +The owner is the one who created the repository, or, in case of an organization, all members of the team "Owners" (which by default includes the creator of the organization). + +The table below gives an overview of what collaborators/teams are allowed to do when granted each of these permission levels: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Task Read Write Admin Owner
View, clone and pull repository
Contribute pull requests
Push to/update contributed pull requests
Push directly to repository
Merge pull requests
Moderate/delete issues and comments
Force-push/rewrite history (if enabled)
Add/remove collaborators to repository
Configure branch settings (protect/unprotect, enable force-push)
Configure repository settings (enable wiki, issues, PRs, update profile)
Configure repository settings in the danger zone (transfer ownership, delete wiki data / repository, archive repository)
\ No newline at end of file