System Roles and Permissions
Different users have different permissions based on their roles and permissions within the organization or project. In public projects and organizations, all logged-in users will enjoy the following permissions:
- Create new issues
- Create pull requests (PRs) in the project
- Post comments (including commenting on issues, PRs, commits, and discussions)
- Clone or download project code
- View project wiki pages
- View organization or project discussions
- View the organization's public boards
In addition to the permissions of public projects, there are some features not restricted by the permission system:
- Lightweight PR creation does not depend on code push permissions. When lightweight PRs are enabled in the project, any platform-logged user can submit a lightweight PR.
- Protected branches and protected tags will follow the effective protection rules.
System Roles
In GitCode, system roles are divided into the following types:
- Administrator (Owner): The administrator of the organization, who has all permissions and final decision-making authority.
- Maintainer: A maintainer of the project or organization, responsible for daily maintenance work, such as handling issues and PRs.
- Developer: Write and submit code, participate in development and discussions.
- Reporter: Report issues, provide feedback, and participate in project discussions.
- Guest: Browse project permissions, participate in discussions in the public discussion area.
Organization Administrator
| Resource | Permissions | | | | | | | |
|---|
| Organization | Delete | Settings | Update | | | | | |
| Project | Create | Fork | Update | Delete | Settings | Archive | Transfer | |
| Code | Push | Download | | | | | | |
| Members | Invite | Update | Remove | | | | | |
| Issues | Create | Update | Close/Open | Pin | Lock | | | |
| Labels | Create | Update | Delete | | | | | |
| Milestones | Create | Update | Delete | | | | | |
| Branches | Create | Delete | | | | | | |
| Tags | Create | Delete | | | | | | |
| Pull Requests | Create | Update | Review | Approve | Merge | Close | Reopen | Test |
| Comments | Create | Resolve | | | | | | |
| Discussions | Create | Update | Lock | Pin | Close/Open | | | |
| Kanban Boards | Create | Update | Delete | Close/Open | | | | |
The highest role for project members is the administrator, and administrator permissions can only be inherited from the organization; they do not support adding "administrator" permissions directly in the project.
- Creators can update the title and description of issues and PRs, and also close or reopen them.
- The author of a comment can edit and update the comment.
- The member lists of the organization and the project can only be viewed by members of the organization and the project.
- Label permissions include both organization labels and project labels.
- Security issues submitted by users can only be viewed by the issue author and project members.
- The permissions of the project wiki are the same as those for pushing code to the project.
- The permissions of the project releases are the same as those for project tags.
- Resolving in a comment refers to resolving marked issues during PR code reviews.
Organization/Project Maintainers
| Resource | Permissions | | | | | | | |
|---|
| Organization | Settings | | | | | | | |
| Project | Create | Fork | Settings | | | | | |
| Code | Push | Download | | | | | | |
| Members | Invite | Update | Remove | | | | | |
| Issues | Create | Update | Close/Open | Pin | Lock | | | |
| Labels | Create | Update | Delete | | | | | |
| Milestones | Create | Update | Delete | | | | | |
| Branches | Create | Delete | | | | | | |
| Tags | Create | Delete | | | | | | |
| Pull Requests | Create | Update | Review | Approve | Merge | Close | Reopen | Test |
| Comments | Create | Resolve | | | | | | |
| Discussions | Create | Update | Lock | Pin | Close/Open | | | |
| Kanban Boards | Create | Update | Delete | Close/Open | | | | |
- The creator of an issue or PR is allowed to update the title and description of the issue or PR, and is allowed to close or reopen the issue or PR.
- The author of a comment is allowed to edit and update the comment information.
- The member lists of the organization and the project can only be viewed by organization and project members.
- Label permissions include both organization labels and project labels.
- Security issues submitted by users can only be viewed by the issue author and project members.
- The permissions of the project wiki are consistent with the code push permissions of the project.
- The permissions of the project releases are consistent with the tag permissions of the project.
- Resolving in a comment refers to resolving marked issues during PR code reviews.
Organization/Project Developers
| Resource | Permissions | | | | | | |
|---|
| Project | Fork | | | | | | |
| Code | Push | Download | | | | | |
| Issues | Create | Close/Open | | | | | |
| Branches | Create | Delete | | | | | |
| Tags | Create | | | | | | |
| Pull Requests | Create | Review | Merge | Test | Close | | |
| Comments | Create | Resolve | | | | | |
| Discussions | Create | Update | Close/Open | | | | |
| Kanban Boards | Create | Update | Close/Open | | | | |
- The creator of an issue or PR is allowed to update the title and description of the issue or PR, and is allowed to close or reopen the issue or PR.
- The author of a comment is allowed to edit and update the comment information.
- The member lists of the organization and the project can only be viewed by organization and project members.
- If "Prevent developers from creating tags" is selected, they will not be able to create tags.
- If "Prevent developers from creating branches" is selected, they will not be able to create branches.
- Security issues submitted by users can only be viewed by the issue author and project members.
- The permissions of the project wiki are consistent with the code push permissions of the project.
- The permissions of the project releases are consistent with the tag permissions of the project.
- Resolving in a comment refers to resolving marked issues during PR code reviews.
Organization/Project Reporters
| Resource | Permissions | | | | | | |
|---|
| Project | Fork | | | | | | |
| Code | Download | | | | | | |
| Issues | Create | Close/Open | | | | | |
| Pull Requests | Test | | | | | | |
| Comments | Create | Resolve | | | | | |
| Discussions | Create | Close/Open | | | | | |
- The author of a comment is allowed to edit and update the comment information.
- The member lists of the organization and the project can only be viewed by organization and project members.
- Security issues submitted by users can only be viewed by the issue author and project members.
- Resolving in a comment refers to resolving marked issues during PR code reviews.
Organization/Project Guests
| Resource | Permissions | | | | | |
|---|
| Issues | Create | | | | | |
| Comments | Create | | | | | |
| Discussions | Create | | | | | |
- The author of a comment is allowed to edit and update the comment information.
- The member lists of the organization and the project can only be viewed by organization and project members.
- Security issues submitted by users can only be viewed by the issue author and project members.