Title: Account OWNER receives 403 when creating a Vercel preview deployment through API

Hello Vercel team,

I'm trying to update an existing protected preview deployment for my project rls-raphael-training-synthetic.

My authenticated account, stevenventer7-1825, is confirmed as the OWNER of the team stevenventer7-1825s-projects.

The project exists, its current deployments work, and Vercel Authentication is enabled.

However:

1. Calling POST /v13/deployments with target: "preview" returned HTTP 403: "You don't have permission to create a Production Deployment for this project."
2. Calling GET /v7/deployments with the explicit team/project identifiers also returned HTTP 403.
3. The new deployment was not created.

Request IDs:

• Deployment creation: iad1:gru1:iad1:sfo1::wcsl4-1794108590906-4dac8a7e0076
• Deployment listing: iad1:gru1:iad1:sfo1::2h79m-1794108845646-661aa668ab9e

I only want to create a preview deployment, without modifying production.

Could you clarify why the preview request is being classified as a production deployment, and whether this is an API target-handling or integration-permission issue?

Further investigation shows that GET /v7/deployments returns HTTP 403 when the existing project ID and its owning team ID are supplied explicitly. The same request succeeds when the team ID is omitted. The account is confirmed as OWNER, and the project already has successful Preview deployments. Could Vercel investigate whether explicit team scoping or integration authorization is causing these inconsistent results?

Thank you.