I love Vercel, pay for the Pro account, and use it for all of my own projects.
I also recommend it to my clients when I do freelancing / work-for-hire.
Some of my clients are non-technical and don’t have their own GitHub accounts. As such, I simply:
Use my own GitHub account to build their projects.
Push to their individual Vercel account.
Given that Vercel requires a 1-to-1 relationship between a GitHub account and a Vercel account … this situation is very, very frustrating.
Any possibility of a future where we can use the same GitHub account to push code to multiple different Vercel accounts? I’m not talking about signing in with GitHub OAuth or anything … just connecting repos from the same GitHub account to multiple different Vercel accounts for automatic deployment/etc.
Vercel Alum
Welcome to the community, Kenneth!
Unfortunately, Vercel currently enforces a 1:1 relationship between GitHub accounts and Vercel accounts. This is a security design decision, and there’s no public roadmap to change it.
Here are your best options:
Keep one Vercel account and create separate teams for each client.
Help clients create basic GitHub accounts just for hosting their repos (they don’t need to use them actively)
I understand this adds friction to your workflow. The teams approach tends to work best for most freelancers since you can manage everything from one account.
so the solution is to have people that never touched code to create a github account , then we will have to login in their account to manage the hosting etc , rather that allow single GitHub account to multiple vercel ? This decision needs to go back on the drawing board its not efficient at all , and other hosting providers allow you to have a single Github/Gitlab to multiple accounts .
Please revisit this will be a huge win if implemented
This is absolutely egregious. I am managing multiple clients from the same github account (as github enables SSO via different emails) and this model kills my workflow. The security reason is mute, as many providers have solved this.
It is so frustrating, I deal with this problem every time and it is absolutely trash to manage each client's account separately, manually deploying new commits by logging into client's account each time. Please fix it guys.
What security design decision is this 1:1 relationship "feature" trying to achieve? It's not like Vercel is blocking connecting a second account until we disconnect the first one (I can imagine this could prevent potential account mis-linking by a bad actor or so). But no, Vercel just silently unlinks any previously linked account.
This must be fixed! If this is a design decision, it's a poor one.
This makes zero sense and even causes CI deployments EXPECTED TO WORK to start failing because of the account "un-linkage"... It's absolutely unfriendly how this is implemented. I highly doubt this is a security-wise decision, and it sounds like a lazy post-mortem excuse... "Oops, a long long time ago, we didn't have the foresight to consider many-to-one relationships, so now we're technically limited to a one-to-one design and we have to find an excuse".
I had my GitHub account linked to Vercel A, which is what I use to deploy commits that I authored and committed with Email A.
Now I also have Vercel B, in which I wanted to deploy commits I authored and committed with Email B. Since both email addresses are linked to the same GitHub account, I proceeded to connect it to Vercel B as well.
The deployments in Vercel B works, but guess what.... now the deployments in Vercel A started failing silently, EVEN IF THEY WERE USING A COMPLETELY DIFFERENT EMAIL ADDRESS!
One, I got NO WARNING about this disconnection in Vercel A when connecting my GitHub in Vercel B. If I didn't check, I'd have no clue. Even after I found out, I had no idea what was going on and I was stumped why the deployments are failing even if the email addresses are different. It was only by random chance that I noticed that the GitHub account is unlinked in Vercel A.
Two, when I click "Fix & Redeploy" in the blocked build's popup about the deployment author data, it said "This will add another user to your team, BILLED AT $20/MONTH". So not only does this sound lazy, it also sounds like an easy CASH GRAB, which is a high motivation to avoid fixing this and allowing multiple Vercel accounts for the same GitHub accounts.
Vercel & , this sounds like a very shady marketing/profiteering decision and you still haven't explained what "security shortcoming" this is supposed to fix.
FWIW, you can set up GitHub Actions to indirectly deploy your projects into Vercel without connecting your GitHub account.
