Simplified permissions for tagging targets with Access for Infrastructure
Tagging targets through the Infrastructure Access Targets API now requires only the Zero Trust Write API token permission instead of both Zero Trust Write and Tag Write permissions. This simplifies the permission model for API-based target management.
You can now tag targets using only the Zero Trust Write API token permission. Previously, tagging targets through the API required both Zero Trust Write and Tag Write permissions on the API token.
This change applies to inline target tagging through the Infrastructure Access Targets API. Tagging resources through the general Resource Tagging API still requires the Tag Admin, Tag Write, or equivalent role.
For more information, refer to Tag targets.
Source: original entry ↗
More from Cloudflare
Follow Cloudflare to get its new changes in your feed and email digest.
Web Analytics: Deeper Core Web Vitals Diagnostics with LCP & INP Sub-Part Metrics
Real User Monitoring in Web Analytics now breaks down Largest Contentful Paint (LCP) and Interaction to Next Paint (INP) into their constituent phases, plus splits connection time into TCP and TLS components. These sub-part metrics are available in the dashboard and queryable through the GraphQL Analytics API to help identify which specific area is impacting page performance.
Cloudflare API MCP server sends Workers Issues as MCP Events
The Cloudflare API MCP server now exposes Workers Issues as MCP Events through webhook subscriptions, allowing agents to receive real-time notifications when production failures are detected without polling. Clients can subscribe to cloudflare.alert.workers_observability_real_time_issue scoped to an account or individual Worker.
Cloudflare One Client for Windows - Hotfix for split tunnel disconnections
This release resolves an issue where the Windows Cloudflare One Client could repeatedly disconnect and reconnect when a split tunnel configuration with hostname-based entries failed to apply.