GitHub Teams and Multiple Free Accounts

[Time0o]

Select Topic Area

Question

Body

The terms of service state that you may not create more than one free non-machine account. If my employer requires me to maintain a separate account that is not itself on any paid plan but IS a member of their organization that itself pays for GitHub teams, is that a TOS violation?

There are reports on the Internet of accounts being suspended but never in the context of some private+business account combination, is this because this is explicitly allowed or just tolerated?

[DevFoxxx]

Hi @Time0o, technically, it’s a gray area, but practically, you are safe.

The ToS 'one free account' rule is primarily aimed at preventing abuse (like spamming, botting, or gaming GitHub Actions). Since your work account is a member of a paid Organization, you are essentially a 'paid seat,' and GitHub differentiates this from someone just hoarding multiple free accounts.

Tolerated vs. Allowed: It is widely tolerated and common practice. GitHub rarely bans users for having a clear 'Work vs. Personal' distinction, especially when an Enterprise/Team plan is involved.
The 'GitHub Way': GitHub officially recommends using one account for everything and simply adding your work email to it, but many companies enforce separate accounts for security/compliance.
Why people get banned: suspensions usually hit users creating multiple free accounts to bypass rate limits or manipulate repo stats.

As long as you aren't using both accounts to double-dip into free tier benefits (like free Actions minutes), you shouldn't have any issues.

[mohamedshiras]

Although maintaining a separate free GitHub account for your employer technically violates the strict wording of their Terms of Service, it is widely tolerated in practice. GitHub primarily enforces this rule to prevent malicious behavior like spamming or bypassing free-tier limits, rather than to penalize developers for legitimately separating their work and personal projects. However, their officially recommended alternative is to maintain a single personal account, attach your work email to it, and configure your local Git environment to route commits and notifications appropriately.

[Celestial-GeekStarLord]

here's a general breakdown:

Multiple Accounts on Free Plan:
GitHub's Terms of Service (ToS) generally allow only one free account per individual user, specifically for personal use. This is where the limitation comes in: creating multiple personal free accounts typically violates this rule. However, the key distinction is whether the accounts are used for personal vs. business purposes.

Business-Related Accounts (GitHub Teams):
If your employer is paying for a GitHub Teams plan and you are required to have an additional account that is tied to their organization (even if it's not paid individually), this likely falls under the business use case. GitHub typically allows organizations to manage multiple accounts for employees as long as those accounts are not violating the personal use restriction on a free account.

If your employer is paying for the GitHub Teams subscription, your account as a part of that organization should not violate the ToS, as long as the account is used for business purposes.

Your free personal account (unrelated to business) should remain separate and not exceed the one account limitation.

Why Suspensions Might Happen:
The suspensions or reports of account bans usually occur when a user creates multiple free accounts that are primarily for personal use and violate the "one free account" rule. However, if your account is used for legitimate work purposes under a paid organization, this might not lead to suspension unless there are other violations (e.g., misuse of services, spam, or inappropriate content).

Explicitly Allowed or Tolerated:
The practice of combining personal and business accounts (i.e., one free account for personal use and a separate business account under a paid organization) isn’t explicitly allowed or disallowed in GitHub’s documentation. However, GitHub generally tolerates it as long as:

The free personal account adheres to the personal use guidelines.

The business account is legitimately used under the organization’s plan (GitHub Teams, GitHub Enterprise, etc.).

Final Takeaway:

It seems that having a separate personal account and a business account under an employer's GitHub Teams plan should not be a violation of GitHub's Terms of Service as long as you're not violating other policies. However, it's always a good idea to reach out to GitHub directly to clarify your specific use case and avoid any misunderstandings.

[AakashSingh07]

This is actually a really interesting question, because the wording in the ToS can sound stricter than what happens in practice.

From what I’ve seen, GitHub’s “one free account” guideline is mainly intended to prevent abuse cases (for example people creating multiple accounts to bypass limits, spam, automate actions, or manipulate CI resources). It isn’t really designed to punish normal workflows where someone has a clear separation between personal and work environments.

In many companies it’s quite common for developers to have:

• a personal GitHub account for open-source projects
• a separate work account that is added to an organization using GitHub Teams / Enterprise

Even though both accounts might technically be “free” accounts individually, the important detail is that the work account is attached to a paid organization seat. In that scenario the account is essentially operating within the company’s paid environment rather than acting like a second free account created for platform abuse.

Another practical signal GitHub usually looks at is intent and behavior. If both accounts are used for clearly different purposes (personal vs company work) and are not used to bypass service limits, it’s generally treated as normal usage.

What I’m curious about though — and maybe you can clarify this part — is why your employer requires a completely separate account instead of inviting your personal account to the organization. Most companies simply add your existing account to their organization and control access through Teams and permissions.

Is there a specific security or compliance policy that requires employees to maintain a separate identity for company work? I’ve seen that approach in a few regulated environments, but it’s not the usual setup.

Would be interesting to hear how your company is structuring this and whether others here have seen the same policy.