cloudflare-one

1# Cloudflare One
2 
3Before citing limits, settings, API fields, category IDs, or exact UI paths, retrieve current information from the [Cloudflare One docs](https://developers.cloudflare.com/cloudflare-one/index.md), the Cloudflare docs MCP server, or the Cloudflare API schema.
4 
5## Workflow
6 
71. Classify the ask: architecture, configuration, troubleshooting, migration, or review.
82. Gather context: account ID, users/sites/apps, identity provider, SCIM/group sync, device management, traffic path, compliance constraints, and rollout blast radius.
93. Retrieve only the current docs needed for the products involved: Access, Gateway, WARP/device client, Tunnel/Mesh, Cloudflare WAN, DLP, CASB, device posture, or identity.
104. If account access is available, inspect existing resources before proposing or making changes: Access apps/policies/groups/IdPs, Gateway rules/lists/categories, device profiles/posture checks, tunnels/routes, DNS/resolver settings, and locations/sites.
115. Propose the change set with prerequisites, validation, and rollback. For risky changes, stage disabled or scoped to a pilot group/site unless the user explicitly asks otherwise.
12 
13## Assessment Prompts
14 
15Use these to avoid jumping straight to configuration. Ask only the prompts relevant to the user's task.
16 
17### Architecture and Current State
18 
19- Sites and users: offices, branches, data centers, VPCs, remote users, contractors, user counts, and current connectivity model.
20…