From 104f25cb51682e8b1fc5a07542b7a6d0073d0159 Mon Sep 17 00:00:00 2001 From: Ivan Calandra <12525997+ivan-paleo@users.noreply.github.com> Date: Wed, 30 Sep 2020 08:48:58 +0200 Subject: [PATCH] Changes requested by lhinderberger (table missing... next commit) --- content/collaborating/create-organization.md | 23 ++++++++++++++------ 1 file changed, 16 insertions(+), 7 deletions(-) diff --git a/content/collaborating/create-organization.md b/content/collaborating/create-organization.md index 40aea30..825d82a 100644 --- a/content/collaborating/create-organization.md +++ b/content/collaborating/create-organization.md @@ -11,7 +11,7 @@ An organization is a group of users that have access to a shared account. As suc Everyone can create organizations on Codeberg for free. The following sections will show you how to create and manage an organization. -> Details about the roles involved (owner, admin, member...) are given in the sections [Teams](#teams) and [People](#people) below. +> Details about the roles involved (owner, admin, member...) are given in the section [Access rights](#access-rights) below. ## Create an Organization @@ -22,7 +22,7 @@ On your Dashboard, click on the `+` next to your avatar and select `New Organiza new-orga -In the new form, choose a name for your organization (here `PolarClub`) and define its visibility. Finally, choose what the administrators of repositories can do: if the box is ticked, repository administrators will be able to grant any team access to the repository (see [Teams](#teams) below for details on repository administrators). +In the new form, choose a name for your organization (here `PolarClub`) and define its visibility. Finally, choose what the administrators of repositories can do: if the box is ticked, repository administrators will be able to grant any team access to the repository (see [Access rights](#access-rights) below for details on repository administrators). Confirm by clicking the green `Create Organization`: @@ -88,7 +88,7 @@ The `Teams` tab gives you an overview of the different teams, of their members a teams -When you create an organization, a team `Owners` is created and you are automatically added to this team. Members of the Owners' team have all rights: they can edit (including delete) the organization, add or remove teams and members, define the access rights of each team, and they have full administrator rights to all repositories of the organization. +When you create an organization, a team `Owners` is created and you are automatically added to this team. Members of the Owners' team have all rights (see [Access rights](#access-rights) below for details). Click the green `+ New Team` to create a new team. Define its name, permissions and access in the new form: @@ -98,10 +98,10 @@ 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. In this case, 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). +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 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. Administrator rights are also required to add or remove collaborators and teams to the repositories. +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. If you belong to the team `Owners`, you can edit a team. For this, go to the `Teams` tab and click on the team you want to edit: @@ -131,7 +131,16 @@ The visibility of the members can also be edited here: `Hidden` means that the m profile -Members can have one of two roles: `Member` or `Owner`. It is also shown here whether each member has activated the two-factor authentification (`2FA`, see [Setting up Two-factor Authentication](/security/2fa)). 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: + + + + + +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).