[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Help](/c/help/9)

# Automatic production deployments not working after upgrade to Pro

107 views · 0 likes · 2 posts


Jsuarez Keepup (@jsuarez-keepup) · 2024-08-20

Hello there

Until a few days ago we had a hobby account with a few projects integrated with GitHub. Our team was able to trigger a deployment just by pushing to the main branch.

We upgraded to Pro and now the team can't trigger the deployments as we used to. We just have one seat (mine) the other members of the team didn't need one since by pushing to main it was enough for them.

I read this https://vercel.com/guides/why-aren-t-commits-triggering-deployments-on-vercel#hobby-to-pro-upgrade but I don't see how can I fix it.

Do all the team need to have a Pro seat in order to trigger the deployments now? In case not, how should I configure the account?


Pauline P. Narvas (@pawlean) · 2024-08-21

Hi, @jsuarez-keepup! Welcome to the Vercel Community :smile: 

> Do all the team need to have a Pro seat in order to trigger the deployments now? 

The answer is yes. From [relevant documentation](https://vercel.com/docs/deployments/git#using-pro-teams):

> If the commit author is not a member, the deployment will be prevented, and the commit author can request to join the team. The team owners will be notified and can accept or decline the membership request on the [Members](https://vercel.com/docs/accounts/team-members-and-roles) page in the team Settings.

https://vercel.com/docs/deployments/git#using-pro-teams