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. Each unit has its own set of permissions and capabilities.
| Unit | Description | Available Permissions |
|---|---|---|
| Code | Source code, files, commits, and branches | Read, Write |
| Issues | Bug reports, tasks, and milestones | Read, Write |
| Pull Requests | Code review and collaboration | Read, Write |
| Settings | Repository configuration | Admin |
Permission Levels and Capabilities
Different permission levels grant users specific capabilities within each unit:
| Unit | Read | Write | Admin |
|---|---|---|---|
| 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 | - |
| Settings | - | - | Manage repository settings and access |
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
- Owners can grant permissions to other users
Organization Repositories
For organization repositories, permissions are managed through teams:
Owner Team
- Created automatically when an organization is established
- 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
Admin Team
- Can be created to manage specific repositories
- Members have full access to assigned repositories
- Only owner team or admin team members can create new teams
General Team
- Has customizable unit-level permissions
- Can be scoped to specific repositories or all repositories
- Can be configured to allow or restrict repository creation
- 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.
Last updated on