Skip to content
Tutorials Center
My learning

Topics

Lesson 3 of 36 ยท Getting Started

Cloudflare Account, Plans, Dashboard and API Tokens

Tour the Cloudflare dashboard, compare Free, Pro, Business and Enterprise plans, secure your account with 2FA, and create least-privilege API tokens.

Before adding a domain, it pays to understand how Cloudflare organizes things: accounts, zones, members and plans. A little care at this stage (two-factor authentication, scoped tokens) prevents the kind of mistakes that cost real sites their DNS.

Accounts, zones and members

A user is a person with a login. An account is the container for resources: zones (domains), Workers, R2 buckets, Zero Trust settings and billing. One user can belong to several accounts, for example a personal one and a client's. Inside an account you add members and give each a role (Administrator, Billing, DNS-only, Analytics and so on) so that nobody has more power than they need.

A zone is a domain. Plans such as Free or Pro are attached per zone, while products like Workers and R2 are billed at the account level. Many accounts run dozens of zones, some on Free and a few on Pro or Business.

flowchart TB
  U["User (you)"] --> A["Account"]
  A --> Z1["Zone: example.com (Free)"]
  A --> Z2["Zone: shop.example (Pro)"]
  A --> W["Workers, R2, KV, D1"]
  A --> ZT["Zero Trust"]
  A --> M["Members and roles"]

Resources live in an account; plans attach to zones.

Creating and protecting your account

Sign up at the Cloudflare website with an email address and a strong, unique password. Then, before anything else:

  1. Verify your email so you can receive security notices.
  2. Turn on two-factor authentication under My Profile > Authentication. A hardware security key or an authenticator app is better than SMS codes.
  3. Save the recovery codes somewhere offline.
  4. For teams, invite colleagues as members instead of sharing one login.

An attacker who takes over your Cloudflare account can change DNS and redirect your whole site, so this account deserves the same care as your domain registrar.

The dashboard map

The dashboard changes layout from time to time, but the structure stays recognizable. After you pick an account you see a left menu with account-level products (Workers & Pages, R2, Zero Trust, Manage Account). After you open a zone, the menu shows zone-level features:

Area What you do there
Overview See status, nameservers, quick actions, the plan
Analytics & Logs Traffic, security events, performance
DNS Records, DNSSEC, settings
Email Email Routing
SSL/TLS Encryption mode, certificates, HSTS
Security WAF, rate limiting, bots, DDoS
Caching Cache rules, purge, tiered cache
Rules Redirects, transforms, configuration rules
Workers Routes Attach Workers to URL patterns
Network HTTP/3, WebSockets, IPv6 settings

Use the search box at the top; it finds settings by name and is usually faster than clicking through menus.

Plans compared

Zone plans are Free, Pro, Business and Enterprise. Exact limits and prices change, so read the current plans page, but the shape stays the same:

  • Free: DNS, a universal TLS certificate, CDN, unmetered DDoS mitigation, a few WAF and other rules, basic analytics. Excellent for personal sites, blogs and learning.
  • Pro: more rules, image optimization features, better WAF controls and analytics, support by ticket.
  • Business: higher limits, custom certificates, a stronger uptime commitment, more flexible caching and security options.
  • Enterprise: negotiated contract, the highest limits, advanced bot management, log delivery, dedicated support and many extras.

The Workers and R2 platforms have their own free allowances and paid plans, separate from the zone plan.

JS Stand-in: pick a plan from requirements

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The numbers above are invented for the exercise. The habit to keep: write down the capabilities you need, then pick the cheapest plan that provides them.

API tokens, not the global key

Everything you can click in the dashboard can also be done with the Cloudflare API, base URL https://api.cloudflare.com/client/v4/. Authenticate with an API token sent as a bearer token:

Terminal
curl -s https://api.cloudflare.com/client/v4/user/tokens/verify \
  -H "Authorization: Bearer $CLOUDFLARE_API_TOKEN"

Create tokens under My Profile > API Tokens > Create Token. A token is made of:

  • Permissions, such as Zone: DNS: Edit or Account: Workers Scripts: Edit.
  • Resources, the zones or accounts it applies to (for example only example.com).
  • Optional IP filtering and an expiry date.

Prefer a narrow token per purpose (one for CI that deploys a Worker, another for a script that edits one zone's DNS) over the legacy Global API Key, which acts as you with full power. Store tokens in environment variables or a secret manager, never in Git. The token value is shown only once.

Every API response has the same envelope:

JSON
{
  "success": true,
  "errors": [],
  "messages": [],
  "result": { }
}

Lists add result_info with page, per_page and total_count for pagination.

JS Stand-in: build an API request without sending it

Press Run (or Ctrl + Enter) to see the console output here.

No output.

In the DNS API, ttl: 1 means "automatic". Using placeholders keeps secrets out of examples; never paste a real token into a web page or a shared chat.

Other ways to manage Cloudflare

  • Wrangler, the command-line tool for Workers, R2, KV and D1 (chapters 5 and 6).
  • Terraform and other IaC tools, using Cloudflare's provider so settings live in version control (chapter 8).
  • SDKs for TypeScript, Python and Go that wrap the REST API.
  • Audit logs under Manage Account > Audit Log show who changed what and when.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. Where are zone plans (Free, Pro, Business) applied?

    A plan belongs to a zone, so one account can have a Free zone and a Pro zone.
  2. 2. Why prefer an API token over the Global API Key?

    Scoped tokens limit the damage if one leaks.
  3. 3. What is the correct way to send an API token?

    Use the Authorization header with the Bearer scheme; URLs end up in logs.
  4. 4. What should you do right after creating an account?

    Account takeover would let an attacker change DNS for every zone, so 2FA comes first.
  5. 5. In the DNS records API, what does ttl: 1 mean?

    The value 1 is Cloudflare's way of saying 'automatic TTL'.

Summary

  • Accounts hold resources and members; plans attach to zones.
  • Turn on 2FA first; use roles for teammates.
  • The dashboard splits into account-level products and zone-level settings; use search.
  • Use scoped API tokens with bearer auth, never the Global API Key, and keep them out of Git.

Next: Adding a site to Cloudflare