Getting started with GitHub Team

With GitHub Team groups of people can collaborate across many projects at the same time in an organization account.

In this article

This guide will walk you through setting up, configuring and managing your GitHub Team account as an organization owner.

Part 1: Configuring your GitHub account

As the first steps in starting with GitHub Team, you will need to create a user account or log into your existing account on GitHub, create an organization, and set up billing.

1. About organizations

Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features. For more information on the features of organizations, see "About organizations."

2. Creating an organization and signing up for GitHub Team

Before creating an organization, you will need to create a user account or log in to your existing GitHub account. For more information, see "Signing up for a new GitHub account."

Once your user account is set up, you can create an organization and pick a plan. This is where you can choose a GitHub Team subscription for your organization. For more information, see "Creating a new organization from scratch."

3. Managing billing for an organization

You must manage billing settings, payment method, and paid features and products for each of your personal accounts and organizations separately. You can switch between settings for your different accounts using the context switcher in your settings. For more information, see "Switching between settings for your different accounts."

Your organization's billing settings page allows you to manage settings like your payment method, billing cycle and billing email, or view information such as your subscription, billing date and payment history. You can also view and upgrade your storage and GitHub Actions minutes. For more information on managing your billing settings, see "Managing your GitHub billing settings."

Only organization members with the owner or billing manager role can access or change billing settings for your organization. A billing manager is someone who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "Adding a billing manager to your organization."

Part 2: Adding members and setting up teams

After creating your organization, you can invite members and set permissions and roles. You can also create different levels of teams and set customized levels of permissions for your organization's repositories, project boards, and apps.

1. Managing members of your organization

You can invite anyone to be a member of your organization, as long as they have a personal account on GitHub. You can also remove members and reinstate former members. For more information, see "Managing membership in your organization."

2. Organization permissions and roles

Each person in your organization has a role that defines their level of access to the organization. The member role is the default, and you can assign owner and billing manager roles as well as "team maintainer" permissions. For more information, see "Permission levels for an organization."

3. About and creating teams

Teams are groups of organization members that you can create to reflect your company or group's structure with cascading access permissions and mentions. Organization members can send notifications to a team or request reviews, and teams can be visible or secret. For more information, see "About teams."

You can create independent teams or have multiple levels of nested teams to reflect your group or company's hierarchy. For more information, see "Creating a team."

4. Managing team settings

You can designate a "team maintainer" to manage team settings and discussions, among other privileges. For more information, see "Giving "team maintainer" permissions to an organization member."

You can manage code review assignments for your team, change team visibility, manage scheduled reminders for your team, and more in your team's settings. For more information, see "Organizing members into teams."

5. Giving people and teams access to repositories, project boards and apps

You can give organization members, teams, and outside collaborators different levels of access to repositories owned by your organization with granular permission levels. For more information, see "Repository permission levels for an organization."

You can also customize access to your organization's project boards and allow individual organization members to manage your organization's GitHub Apps. For more information, see "Managing access to your organization's project boards" and "Managing access to your organization's apps."

Part 3: Managing security for your organization

You can help to make your organization more secure by recommending or requiring two-factor authentication for your organization members, configuring security features, and reviewing your organization's audit log and integrations.

1. Requiring two-factor authentication

You can view whether your organization members have two-factor authentication enabled and choose to require two-factor authentication in your organization. For more information, see "Requiring two-factor authentication in your organization."

2. Configuring security features for your organization

To keep your organization secure, you can use a variety of GitHub security features, including security policies, dependency graphs, secret scanning and Dependabot security and version updates. For more information, see "Securing your organization" and "Managing security and analysis settings for your organization."

3. Reviewing your organization's audit log and integrations

The audit log for your organization allows you, as an organization owner, to review the actions performed by members of the organization within the last 90 days. For more information, see "Reviewing the audit log for your organization."

You can also review and configure the permission levels for your organization's installed integrations. For more information, see "Reviewing your organization's installed integrations."

Part 4: Setting organization level policies

1. Managing organization policies

You can manage permissions and policies for a number of different actions and features in your organization.

For example, to protect your organization's data and number of paid licenses, you can choose to allow only organization owners to invite outside collaborators to organization repositories. You can also choose to allow or prevent the forking of private repositories owned by your organization. For more information, see "Setting permissions for adding outside collaborators" and "Managing the forking policy for your organization."

For the full list of settings you can configure for your organization, see "Managing organization settings."

2. Managing repository changes

You can configure permissions for creating, transferring and deleting repositories in your organization, including which types members can create. For more information, see "Restricting repository creation in your organization" and "Setting permissions for deleting or transferring repositories."

You can also restrict or grant the ability to change repository visibility. For more information, see "Restricting repository visibility changes in your organization."

3. Using organization-level community health files and moderation tools

You can create default community health files, such as a CONTRIBUTING.md file, a CODE_OF_CONDUCT.md file, or even issue and pull request templates, for your organization. These default files will be used for any repository owned by your organization that does not contain its own file of that type. For more information, see "Creating a default community health file."

GitHub offers multiple tools for moderating and managing your community. For more information, see "Tools for moderating your community."

Part 5: Customizing and automating your work on GitHub

You can use tools from the GitHub Marketplace, the GitHub API, and existing GitHub features to customize and automate your work.

1. Using GitHub Marketplace

GitHub Marketplace contains integrations that add functionality and improve your workflow. You can discover, browse, and install free and paid tools, including GitHub Apps, OAuth Apps, and GitHub Actions, in GitHub Marketplace. For more information, see "About GitHub Marketplace."

2. Using the GitHub API

There are two versions of the GitHub API: the REST API and the GraphQL API. You can use the GitHub APIs to automate common tasks, back up your data, or create integrations that extend GitHub. For more information, see "About GitHub's APIs."

3. Building GitHub Actions

With GitHub Actions, you can automate and customize GitHub's development workflow on GitHub. You can create your own actions, and use and customize actions shared by the GitHub community. For more information, see "Learn GitHub Actions."

4. Publishing and managing GitHub Packages

GitHub Packages is a software package hosting service that allows you to host your software packages privately or publicly and use packages as dependencies in your projects. For more information, see “Introduction to GitHub Packages."

Part 6: Participating in GitHub's community

There are many ways to participate in the GitHub community. You can contribute to open source projects, interact with people in the GitHub Community Support, or learn with GitHub Learning Lab.

1. Contributing to open source projects

Contributing to open source projects on GitHub can be a rewarding way to learn, teach, and build experience in just about any skill you can imagine. For more information, see “How to Contribute to Open Source" in the Open Source Guides.

You can find personalized recommendations for projects and good first issues based on your past contributions, stars, and other activities in Explore. For more information, see “Finding ways to contribute to open source on GitHub."

2. Interacting with the GitHub Community Support

You can connect with developers around the world in GitHub Community Support to ask and answer questions, learn, and interact directly with GitHub staff.

3. Learning with GitHub Learning Lab

You can learn new skills by completing fun, realistic projects in your very own GitHub repository with GitHub Learning Lab. Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot.

For more information, see “Git and GitHub learning resources."

4. Supporting the open source community

GitHub Sponsors allows you to make a monthly recurring payment to a developer or organization who designs, creates, or maintains open source projects you depend on. For more information, see “About GitHub Sponsors."

5. Contacting GitHub Support

GitHub Support can help you troubleshoot issues you run into while using GitHub. For more information, see “About GitHub Support."

Further reading

Did this doc help you?Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.