diff --git a/assets/images/collaborating/invite-collaborators/add-collaborator.webp b/assets/images/collaborating/invite-collaborators/add-collaborator.webp new file mode 100644 index 0000000..592aa3f Binary files /dev/null and b/assets/images/collaborating/invite-collaborators/add-collaborator.webp differ diff --git a/assets/images/collaborating/invite-collaborators/collaborator-rights.webp b/assets/images/collaborating/invite-collaborators/collaborator-rights.webp new file mode 100644 index 0000000..ae29758 Binary files /dev/null and b/assets/images/collaborating/invite-collaborators/collaborator-rights.webp differ diff --git a/assets/images/collaborating/invite-collaborators/settings.webp b/assets/images/collaborating/invite-collaborators/settings.webp new file mode 100644 index 0000000..390ac44 Binary files /dev/null and b/assets/images/collaborating/invite-collaborators/settings.webp differ diff --git a/content/collaborating/create-organization.md b/content/collaborating/create-organization.md index dc60b11..8fc28ef 100644 --- a/content/collaborating/create-organization.md +++ b/content/collaborating/create-organization.md @@ -99,7 +99,8 @@ 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 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. @@ -137,18 +138,17 @@ Finally, you can choose to leave the organization from here. ## Access rights -The table below gives an overview of the rights of the different types of teams: +The table below gives an overview of the permission system for organizations based on teams: - - - + + @@ -156,85 +156,71 @@ The table below gives an overview of the rights of the different types of teams: - - - - - - - - - - - - - - - - - - - - - + + + - - - - + + + - - + + + + + + + + + + + + + + - - - - - - - - - - - - - - - - + + - - - + + + + + + + + + + -
- 1 Access to specific sections can be restricted by owners. - 2 If allowed by owners (see box "Create repositories" in team settings). + + * Access to specific sections can be restricted by owners.
Task Team "Owners" Task Other Teams Team "Owners"
Read access Admin access
Edit/delete organization
Add/remove team or member
Define access rights of teams
View and clone repository * * * 1 1 1
Push to repository
Pull from repository
Add collaborators to repository
Edit repository settings (excluding Danger Zone)
Edit repository settings from the Danger Zone
Create repository 2 2 2
Edit the repository created by the member (excluding Danger Zone)
Edit the repository created by the member (including Danger Zone) Edit/delete organization
Add/remove collaborator to the repository created by the member Add/remove team or member
Define access rights of teams
-When owners allow members of a team to be able to create new repositories for the organization, 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 then be added as a collaborator to the repository with administrator rights (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 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). +