Organizations: The Foundation of Team Collaboration
Organizations serve as the foundation for team-based collaboration in APIGIT:
- Organizations can own API repositories, similar to individual users
- Teams are created and managed within organization boundaries
- Teams collaborate on organization repositories according to their assigned permissions and visibility settings
A subscription account can host multiple organizations, allowing you to create separate workspaces for different departments, projects, or functional groups within your enterprise.
Plan Limits
| Plan | Organizations | Teams per organization |
|---|---|---|
| Free | Not available | Not available |
| Team | 5 | 5 |
| Enterprise | 20 | 25 |
Key Benefits of Organizations
- Centralized Repository Management: Maintain all related repositories under one organizational roof
- Hierarchical Team Structure: Create specialized teams with appropriate access levels
- Scalable Collaboration: Easily add new members and adjust permissions as projects evolve
- Departmental Separation: Keep distinct business units or projects isolated when necessary
Managing Organizations
Creating Organizations
The account owner and account admins can create organizations:
- Click Organization in the top navigation bar
- Click Create Organization
- Enter the Organization Name and Description, then choose Public or Private (visible only to organization members)

Viewing Account Organizations
The Account Organizations tab of the Billing & Plan page is a read-only overview of the organizations in your account. It lists each organization with its teams, members, repositories, creation and update dates, and description.

The Organization Page
Click an organization to open it. Everyone in the organization sees the first three tabs. Governance and Setting are shown to owner team members only.
| Tab | What it is for |
|---|---|
| Repositories | The organization’s repositories. Use Create Org Repository to add one |
| Teams | The organization’s teams. See Manage Teams |
| Members | Everyone in the organization, with their Member Role and Membership Visibility |
| Governance | API governance for the organization. See API Governance |
| Setting | Rename the organization, edit its details and visibility, or delete it |


The Email column is shown only when the API returns addresses you may see. Otherwise the list shows usernames alone.
Organization Lifecycle
When creating a new organization:
- An owner team is automatically created
- The creator becomes the first member of this team
- The organization becomes available for repository creation and team setup
To delete an organization, open its Setting tab and use Delete This Organization in the Danger Zone. Only owner team members can do this.
When deleting an organization:
- All repositories within the organization will be deleted
- All teams associated with the organization will be disbanded
- Member associations with the organization will be removed
Note: Organization deletion is permanent and cannot be undone. Make sure to back up any important repositories before deleting an organization.
Next Steps After Creating an Organization
Once an organization is created:
- Set up teams with appropriate members
- Create repositories within the organization
- Configure team permissions for each repository
- Begin collaborating on your API development projects