Owning Multiple GitHub Accounts Violates the Terms — Turning Down a Client's Request for a Separate Work Account
A company I collaborate with on work asked me to create a brand-new GitHub account dedicated to their organization. Doing so would breach the GitHub Terms of Service, so I declined politely. This post covers the exchange, the underlying clause, and the compliant alternative that keeps everyone happy.
What Happened
The specific ask was not “invite your existing account into our GitHub Organization” but “please create a separate account exclusively for our company.” At first glance this looks like a routine onboarding step. It is not.
If I had created that second account, the party in breach of the Terms would not be the client company. It would be me, the individual who created and maintains a second free account. That is why I declined and explained the reasoning.
What Section B.3 of the Terms Actually Says
Section B (“Account Terms”), subsection B.3 (“Required information”) of the GitHub Terms of Service reads:
One person or legal entity may maintain no more than one free Account (if you choose to control a machine account as well, that’s fine, but it can only be used for running a machine).
The clause is unambiguous: one free personal account per human, one per legal entity, no exceptions for “work” or “client.” The moment someone with an existing personal account creates a second free account for a client, that person is in breach of the Terms.
Both the GitHub Docs published version and the github/site-policy repository confirm that this clause is unchanged as of May 2026.
GitHub’s Own Documentation Recommends One Account
Separately from the Terms, the official docs page Types of GitHub accounts says:
Many people use one personal account for all their work on GitHub.com, including both open source projects and paid employment.
If you’re currently using more than one personal account that you created for yourself, we suggest combining the accounts.
The docs are consistent with the Terms. Users are expected to keep a single personal account for everything, including paid employment. GitHub does not treat “work” and “personal” as two different account slots, and that position has not shifted as of May 2026.
The Only Exception Is a Machine Account
The Terms carve out one narrow exception: a machine account. These are non-human accounts used for CI, bots, or automation, and they have specific properties.
- A named human is responsible for the account
- The account is used only for machine tasks such as build automation, deploy jobs, or bot integrations
- A user may hold one free machine account in addition to their personal one
The account the client asked me to create was a human account for me, personally, to open pull requests and leave review comments. It does not fit the machine account exception at all.
The Right Answer Is Organization Membership
When a company wants “an isolated GitHub identity for our work,” the correct mechanism is not a new personal account. It is inviting the person’s existing personal account into the company’s GitHub Organization.
- The company invites my existing personal account into its Organization as a member
- Access to work repositories is granted through Organization-level teams and permissions
- When the engagement ends, removing me from the Organization instantly revokes access to those repositories
Under a paid plan such as GitHub Team or GitHub Enterprise, my account counts as a paid seat in that Organization. Billing, permission management, and audit all live at the Organization layer, so a second personal account is architecturally unnecessary.
Adding the work email address as a secondary email on the personal account lets commit authorship default to the work email for that organization’s repositories. Enterprise features such as SAML SSO, SCIM, and Audit Log all attach to Organization membership rather than to a duplicated personal account.
How I Declined
Concretely, I told the requesting side something along these lines:
- GitHub’s Terms of Service restrict a person to one free personal account
- GitHub’s own documentation also recommends consolidating multiple personal accounts
- Creating a second personal account for their work would put me in breach
- The correct path is inviting my existing personal account into their Organization
- If they want work commits to carry the work email, I can add it as a secondary email on my personal account
The person on the other side did not intend to push me into a Terms violation. They were following an internal onboarding checklist that assumed a fresh account per contractor. Once I explained the constraint, we switched to Organization membership without friction.
Wrap-Up
- GitHub Terms of Service B.3 restricts a person or legal entity to one free account (unchanged as of May 2026)
- Official GitHub docs also recommend consolidating multiple personal accounts into one
- The only exception is a single machine account for CI or bot use, not a second human account
- The correct mechanism for work is Organization membership, not a new personal account
- Even when the requesting side means no harm, breaching the Terms is on the individual, so it is worth declining politely and proposing the correct alternative
The “please create a dedicated GitHub account for our company” request comes up regularly. As the individual on the receiving end, staying within the Terms is your responsibility, and the correct alternative (Organization invitation) is already built into how GitHub works. There is no reason to break the Terms.
That’s all from confirming with May 2026 GitHub sources that owning multiple accounts still violates the Terms, and declining a client’s request in favor of Organization membership, from the Gemba.