Vercel's support assistant directed this question to the Community after declining to create a human support case. Could a Vercel maintainer confirm the supported behavior, ideally with documentation or an implementation reference?
Goal: set a project's Pre-Production Toolbar to Off while keeping Production Toolbar at Default (inherited), without changing Team settings or Deployment Protection.
A prior operation using Vercel CLI 65.16.0 submitted only {"enablePreviewFeedback":false} to PATCH /v9/projects/{projectId}. A separate Project GET, summarized by our helper, reported both feedback fields as false. A rollback containing only {"enablePreviewFeedback":null} was followed by summaries showing both fields null. The original summary reported both properties absent. An independent Dashboard check after rollback showed both selectors as Default.
Limitation: historical raw Project responses were not retained. Tests of the actual helper passed asymmetric fixtures, but this does not establish what the live transport or backend did. We are not claiming a confirmed platform bug or that Production definitely changed or remained unchanged.
Please clarify:
When enableProductionFeedback is omitted from a PATCH updating enablePreviewFeedback, must its stored override remain untouched? Does the Team control allowing project overrides affect this behavior? What is the supported independent update method?
Are these fields in Project GET stored overrides or resolved/effective values? How do absent, null, false, and true differ? Does enablePreviewFeedback:null clear only Preview's override, and what read-only check independently confirms Production's inherited setting?
For an existing Next.js 16.3.5 Preview, an actual same-origin JavaScript response contained a loader for https://vercel.live/_next-live/feedback/feedback.js. The attempt was blocked by CSP; no successful Feedback download was observed. Supplying x-vercel-skip-toolbar:1 to that exact JS request did not change its fingerprint or remove the attempt. Does project Toolbar Off suppress this kind of loader on an existing deployment, or only HTML injection? Is the loader added at build time or response time, and is redeployment required? We cannot infer the injection stage just from an immutable asset path.
References: https://vercel.com/docs/rest-api/projects/update-an-existing-project https://vercel.com/docs/vercel-toolbar/managing-toolbar
This request is for clarification only, not a request to change an account or run another reproduction. If project-specific evidence is needed, please identify a supported private channel; no credentials, protected artifacts, or customer data are included here.