mirror of
https://github.com/go-gitea/gitea.git
synced 2024-12-16 04:23:36 +08:00
74 lines
4.3 KiB
Markdown
74 lines
4.3 KiB
Markdown
|
---
|
||
|
|
date: "2021-12-13:10:10+08:00"
|
||
|
|
title: "Permissions"
|
||
|
|
slug: "permissions"
|
||
|
|
weight: 14
|
||
|
|
toc: false
|
||
|
|
draft: false
|
||
|
|
menu:
|
||
|
|
sidebar:
|
||
|
|
parent: "usage"
|
||
|
|
name: "Permissions"
|
||
|
|
weight: 14
|
||
|
|
identifier: "permissions"
|
||
|
|
---
|
||
|
|
|
||
|
|
# Permissions
|
||
|
|
|
||
|
|
**Table of Contents**
|
||
|
|
|
||
|
|
{{< toc >}}
|
||
|
|
|
||
|
|
Gitea supports permissions for repository so that you can give different access for different people. At first, we need to know about `Unit`.
|
||
|
|
|
||
|
|
## Unit
|
||
|
|
|
||
|
|
In Gitea, we call a sub module of a repository `Unit`. Now we have following units.
|
||
|
|
|
||
|
|
| Name | Description | Permissions |
|
||
|
|
| --------------- | ---------------------------------------------------- | ----------- |
|
||
|
|
| Code | Access source code, files, commits and branches. | Read Write |
|
||
|
|
| Issues | Organize bug reports, tasks and milestones. | Read Write |
|
||
|
|
| PullRequests | Enable pull requests and code reviews. | Read Write |
|
||
|
|
| Releases | Track project versions and downloads. | Read Write |
|
||
|
|
| Wiki | Write and share documentation with collaborators. | Read Write |
|
||
|
|
| ExternalWiki | Link to an external wiki | Read |
|
||
|
|
| ExternalTracker | Link to an external issue tracker | Read |
|
||
|
|
| Projects | The URL to the template repository | Read Write |
|
||
|
|
| Settings | Manage the repository | Admin |
|
||
|
|
|
||
|
|
With different permissions, people could do different things with these units.
|
||
|
|
|
||
|
|
| Name | Read | Write | Admin |
|
||
|
|
| --------------- | ------------------------------------------------- | ---------------------------- | ------------------------- |
|
||
|
|
| Code | View code trees, files, commits, branches and etc. | Push codes. | - |
|
||
|
|
| Issues | View issues and create new issues. | Add labels, assign, close | - |
|
||
|
|
| PullRequests | View pull requests and create new pull requests. | Add labels, assign, close | - |
|
||
|
|
| Releases | View releases and download files. | Create/Edit releases | - |
|
||
|
|
| Wiki | View wiki pages. Clone the wiki repository. | Create/Edit wiki pages, push | - |
|
||
|
|
| ExternalWiki | Link to an external wiki | - | - |
|
||
|
|
| ExternalTracker | Link to an external issue tracker | - | - |
|
||
|
|
| Projects | View the boards | Change issues across boards | - |
|
||
|
|
| Settings | - | - | Manage the repository |
|
||
|
|
|
||
|
|
And there are some differences for permissions between individual repositories and organization repositories.
|
||
|
|
|
||
|
|
## Individual Repository
|
||
|
|
|
||
|
|
For individual repositories, the creators are the only owners of repositories and have no limit to change anything of this
|
||
|
|
repository or delete it. Repositories owners could add collaborators to help maintain the repositories. Collaborators could have `Read`, `Write` and `Admin` permissions.
|
||
|
|
|
||
|
|
## Organization Repository
|
||
|
|
|
||
|
|
Different from individual repositories, the owner of organization repositories are the owner team of this organization.
|
||
|
|
|
||
|
|
### Team
|
||
|
|
|
||
|
|
A team in an organization has unit permissions settings. It can have members and repositories scope. A team could access all the repositories in this organization or special repositories changed by the owner team. A team could also be allowed to create new
|
||
|
|
repositories.
|
||
|
|
|
||
|
|
The owner team will be created when the organization created and the creator will become the first member of the owner team.
|
||
|
|
Notice Gitea will not allow a people is a member of organization but not in any team. The owner team could not be deleted and only
|
||
|
|
members of owner team could create a new team. Admin team could be created to manage some of repositories, members of admin team
|
||
|
|
could do anything with these repositories. Generate team could be created by the owner team to do the permissions allowed operations.
|