Teams: Role-Based Access Control

Teams are the primary mechanism for implementing role-based access control in APIGIT. Created within organizations, teams allow you to group members and assign permissions based on their roles or responsibilities.

Each organization supports three types of teams, arranged in a hierarchical structure:

Owner Team

The Owner Team, named Owners, sits at the top of the permission hierarchy:

• Automatic Creation: Generated automatically when an organization is established
• Initial Membership: The organization creator becomes the first member
• Permanence: Cannot be deleted and must maintain at least one member
• Access Level: Possesses full control over all organization repositories
• Special Privileges: Can modify organization settings and manage teams and their members

Billing is separate from the Owner Team. Plans and payment are managed by the subscription account owner.

Admin Teams

Admin Teams are teams with Administrator Access:

• Purpose: Delegated administrators for the organization’s repositories
• Access Level: Members have full administrative access to all organization repositories
• Repository Creation: Members can create organization repositories
• Repository Management: Can configure repository settings and access controls

General Teams

General Teams are teams with General Access, and provide customizable, task-specific access:

• Flexible Permissions: No Access, Read, or Write on each unit (Repo Code, Issues, Pull Requests, API Document, Mockserver)
• Repository Scope: All repositories, or Assigned repositories only
• Repository Creation: General teams cannot create organization repositories
• Operational Focus: Members perform day-to-day operations based on assigned permissions
• Scalability: Ideal for project teams, functional groups, or departmental divisions

Managing Teams

Team Administration

To manage teams within an organization:

1. Navigate to the organization’s page
2. Switch to the Teams tab
3. Click a team to open it, or click Create Team to add one

Only owner team members can create, change, or delete teams. The number of teams per organization depends on your plan. See Plan Limits.

The Teams tab lists each team’s permission, repository access, whether it can create organization repositories, and its description.

For members of the Owners team, a team’s page has four sections. Other people see Members and Repositories.

• Members: Add and remove team members
• Repositories: The repositories the team can access
• Setting: The team’s name, description, and access permissions
• Delete Team: Remove the team

Team Configuration Best Practices

When configuring teams, consider these best practices:

• Minimize Owner Team Size: Limit owner team membership to essential personnel
• Use Admin Teams Sparingly: Administrator Access covers every repository in the organization
• Map Teams to Roles: Align general teams with functional roles in your organization
• Review Regularly: Periodically audit team memberships and permissions
• Implement Least Privilege: Grant only the permissions necessary for team members to perform their duties

Team Membership Management

After creating teams, you’ll need to manage their membership:

1. Select the team you wish to modify
2. In the Members section, click Add Member To Team and choose from the colleagues in your subscription account
3. Remove members who no longer require access with the delete icon

Remember that all team members must first be added as colleagues to your subscription account before they can be assigned to teams.