Permissions in APIGIT
APIGIT features a comprehensive permissions system that allows you to control access levels for different users across your repositories. This document explains how permissions work in both individual and organization repositories.
Understanding Units
In APIGIT, a “Unit” refers to a functional module within a repository. A team with General Access is given No Access, Read, or Write on each unit.
| Unit | Description |
|---|---|
| Repo Code | Repository files, commits, and branches |
| Issues | Bug reports, tasks, and milestones |
| Pull Requests | Code review and collaboration |
| API Document | Publishing API documents from the repository |
| Mockserver | Publishing mock servers from the repository |
Permission Levels and Capabilities
Different permission levels grant users specific capabilities within each unit:
| Unit | Read | Write |
|---|---|---|
| Repo Code | View code trees, files, commits, and branches | Push code and create/delete branches |
| Issues | View issues and create new issues | Add labels, assign users, close issues |
| Pull Requests | View and create pull requests | Add labels, assign reviewers, merge/close |
Repository settings are not a unit. Managing settings and access takes administrator access to the repository.
Repository Types and Ownership
Individual Repositories
For individual repositories:
- The creator is the sole owner
- Owners have unlimited rights to modify or delete the repository
Organization Repositories
For organization repositories, permissions are managed through teams:
Owner Team
- Created automatically when an organization is established, with the name Owners
- The organization creator becomes the first member of the owner team
- Cannot be deleted and must have at least one member
- Has full control over all organization repositories
- Only owner team members can create, change, or delete teams and manage their members
Admin Team
- A team with Administrator Access
- Members have full access to all organization repositories
- Members can create organization repositories
General Team
- A team with General Access
- Has customizable unit-level permissions
- Can be scoped to specific repositories or all repositories
- Cannot create organization repositories
- Members can perform operations based on their assigned permissions
Note: Users can belong to multiple teams, with their effective permissions being the combined highest level from all team memberships.