Persistent 403 Forbidden from Vercel Integration Despite Reconnecting and Allowing Access

Hello Vercel Community,

I need help resolving a persistent Vercel integration access issue for our company project.

Company: Extrapurse Innovation Ltd Project: Extrapurse EEMS GitHub repository: https://github.com/extrapurseinnovationltd/extrapurse-web-app Vercel project ID: prj_08ZFcqPvAeaq3fW6U5TuXtbg9mVu

Problem:

Our connected Vercel integration can retrieve some project and deployment information, but requests that explicitly use the Vercel team scope return HTTP 403 Forbidden. The integration's team-list request also returns zero teams.

What we have already tried:

Reconnected the Vercel integration.
Selected “Allow Access” during reconnection.
Confirmed that some unscoped project and deployment API requests succeed.
Confirmed that team-scoped requests continue to fail.

We have not established the exact cause. We need help determining whether this is a team membership, integration authorization/scope, or default-team resolution issue.

Could someone advise how to diagnose and correct this without weakening deployment protection or bypassing authentication?

Thank you.