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

Apply code suggestions

Browse source
This commit is contained in:
Gusted 2022-03-04 00:20:58 +01:00
parent a53a187ee3
commit de72273544
No known key found for this signature in database
GPG key ID: FD821B732837125F
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -110,12 +110,12 @@ The table below gives an overview of what collaborators are allowed to do when g
## 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.
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)).
- 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)).