{"version":"2.1.260","anchor":"vertex-workforce-identity-billing-project-now-requires-user","canonical_anchor":"vertex-workforce-identity-billing-project-now-requires-user","heading":"Vertex Workforce Identity billing project now requires user consent","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/vertex-workforce-identity-billing-project-now-requires-user","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Vertex Workforce Identity billing project now requires user consent\n\nVertex Workforce billing project setting now requires user consent before being pushed remotely.\n\nThe `inferenceVertexWorkforceUserProject` config field (the GCP billing project for Vertex Workforce Identity) now sets `remotePolicy: { requiresUserConsent: true }`, so it can no longer be pushed without the user's consent, matching the stricter handling already applied to other connection fields.\n\n- Area: Auth\n- Names: `inferenceVertexWorkforceUserProject`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}