h759bkyo4/Documentation
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Rework the permissions article

Browse source 
- Rework the permission article, by splitting it into 2 new category's.
The current information would be within the Collaborators section, as
that hasn't changed. The new section is mostly concerned for the new
permissions system that is used for teams. It covers all the permissions
and values that can be selected.
- Resolves #204
This commit is contained in:
Gusted 2022-03-04 00:04:59 +01:00
parent fd44b5335f
commit a53a187ee3
No known key found for this signature in database
GPG key ID: FD821B732837125F
1 changed files with 37 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

41
content/collaborating/repo-permissions.md
View file

@ -8,10 +8,14 @@ eleventyNavigation:
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).
Since Gitea v1.16, you can assign teams different levels of permission for each unit (e.g. issues, PR's, wiki).
The table below gives an overview of what collaborators/teams are allowed to do when granted each of these permission levels:
## Collaborators
There are four permission levels: Read, Write, Administrator and Owner.
The owner is the one who created the repository.
The table below gives an overview of what collaborators are allowed to do when granted each of these permission levels:
<table class="table">
<thead>
@ -101,4 +105,33 @@ The table below gives an overview of what collaborators/teams are allowed to do
</tr>
</tr>
</tbody>
</table>
</table>
## Teams
The permissions for teams are quite configurable. You can specify which organization repository the team has access to. Therefore, you can specify for each unit(a unit refers to a specific subset of a repository, e.g. Code access, Issues, Releases) a different permission level.
Each unit is configured to have one of the 3 permission levels:
- No Access: Members cannot view or take any other action on this unit.
- Read: Members can view the unit and do standard actions for that unit (See the Read column under [Collaborators] (#collaborators)).
- Write: Members can view the unit and execute a writing action for that unit (See the Write column under [Collaborators](#collaborators)).
When a team is configured to have administrator access, when this is specified, you cannot change units. The team will have admin permissions (See the Admin column under [Collaborators](#collaborators)).
Currently, there are six units that can be configured:
- Code, access source code, files, commits, and branches.
- Issues, organize bug reports, tasks, and milestones.
- Pull Requests, access to pull requests, and code reviews.
- Releases, track the project versions and downloads.
- Wiki, access and write documentation.
- Projects, access and manage issues and pull requests in project boards.
There are also two units which can be toggled:
- External Wiki, access to external wiki.
- External Issues, access to the external issue tracker.
A team can be given the permission to create new repositories. When a member of such team creates a new repository, it will get administrator access to the repository.