Teams

What are Teams?

Teams are groups of users within an organization that share access to repositories and have specific permission levels. They help you manage access control efficiently.

Creating a Team

Steps

1. Go to Organization → Settings → Teams
2. Click "New Team"
3. Configure:
   • Team Name: Unique, descriptive name
   • Description (optional): Team purpose
   • Permission Level:
     • Read: Can view and clone
     • Write: Can push changes
     • Admin: Full control
   • Members: Add organization members
   • Repositories: Grant repository access
4. Click "Create Team"

Team Features

Members

Add Members:

1. Go to team page
2. Click "Add Member"
3. Search for organization members
4. Select and add

Remove Members:

1. Find the member in team list
2. Click "Remove"

Repositories

Grant Access:

1. Go to team page
2. Click "Add Repository"
3. Select organization repository
4. Set permission level (overrides team default if needed)

Remove Access:

1. Find repository in team list
2. Click "Remove"

Permission Levels

Read:

• View repository
• Clone repository
• View issues and pull requests
• Comment on issues/PRs
• Cannot push code

Write:

• All Read permissions
• Push to repository
• Create branches
• Create issues and PRs
• Manage issues and labels
• Cannot change settings

Admin:

• All Write permissions
• Manage repository settings
• Manage collaborators
• Delete repository
• Transfer ownership
• Manage webhooks and hooks

Managing Teams

Edit Team

1. Go to team page
2. Click "Settings"
3. Update:
   • Name
   • Description
   • Permission level
   • Members
   • Repository access
4. Save changes

Team Members Can

• View all team repositories
• Collaborate based on permission level
• Participate in code review
• Create and manage issues

Team Owners Can

• Modify team settings
• Add/remove members
• Add/remove repositories
• Change permissions

Best Practices

• ✅ Name teams descriptively (e.g., frontend-devs, devops-team)
• ✅ Use minimum required permissions
• ✅ Regularly review team membership
• ✅ Document team responsibilities
• ✅ Create teams by function or project
• ✅ Audit access periodically

Common Team Structures

By Function

• frontend - Frontend developers
• backend - Backend developers
• devops - Infrastructure and deployment
• qa - Quality assurance
• design - UI/UX designers

By Project

• project-alpha - Team working on Project Alpha
• project-beta - Team working on Project Beta
• mobile - Mobile app team

By Access Level

• maintainers - Full admin access
• developers - Write access
• contributors - Read access

Next Steps

• Understand Permissions
• Learn about Code Review
• Explore Organizations