Docs Collections Release Notes

Last updated: Oct 31, 2025

  • Oct 30, 2025
    • Parsed from source:
      Oct 30, 2025
    • Detected by Releasebot:
      Oct 31, 2025

    Docs Collections by Cloudflare

    Revamped Member Management UI

    Cloudflare updates the Dashboard’s Member Management with a refreshed invite flow, clearer Members Overview, and a new member details view for inherited and active permissions. Administrators can now assign multiple account-scoped policies per member, boosting flexibility and policy alignment with groups.

    What's New

    • Refreshed member invite flow
      We overhauled the Invite Members UI to simplify inviting users and assigning permissions.

    • Refreshed Members Overview Page
      We've updated the Members Overview Page to clearly display:

      • Member 2FA status
      • Which members hold Super Admin privileges
      • API access settings per member
      • Member onboarding state (accepted vs pending invite)
    • New Member Permission Policies Details View
      We've created a new member details screen that shows all permission policies associated with a member; including policies inherited from group associations to make it easier for members to understand the effective permissions they have.

    • Improved Member Permission Workflow
      We redesigned the permission management experience to make it faster and easier for administrators to review roles and grant access.

    • Account-scoped Policies Restrictions Relaxed
      Previously, customers could only associate a single account-scoped policy with a member. We've relaxed this restriction, and now Administrators can now assign multiple account-scoped policies to the same member; bringing policy assignment behavior in-line with user-groups and providing greater flexibility in managing member permissions.

    Original source Report a problem
  • Oct 30, 2025
    • Parsed from source:
      Oct 30, 2025
    • Detected by Releasebot:
      Oct 31, 2025

    Docs Collections by Cloudflare

    Introducing email two-factor authentication

    Cloudflare introduces Email as a new 2FA option, pairing with hardware keys and authenticator apps to reduce risk from lost devices while boosting security. Enable Email 2FA via Profile > Authentication > Set up for smoother account protection.

    Email 2FA now available

    Two-factor authentication (2FA) is one of the best ways to protect your account from the risk of account takeover. Cloudflare has offered phishing resistant 2FA options including hardware based keys (for example, a Yubikey) and app based TOTP (time-based one-time password) options which use apps like Google or Microsoft's Authenticator app. Unfortunately, while these solutions are very secure, they can be lost if you misplace the hardware based key, or lose the phone which includes that app. The result is that users sometimes get locked out of their accounts and need to contact support.

    Today, we are announcing the addition of email as a 2FA factor for all Cloudflare accounts. Email 2FA is in wide use across the industry as a least common denominator for 2FA because it is low friction, loss resistant, and still improves security over username/password login only. We also know that most commercial email providers already require 2FA, so your email address is usually well protected already.

    You can now enable email 2FA on the Cloudflare dashboard:

    • Go to Profile at the top right corner.
    • Select Authentication.
    • Under Two-Factor Authentication, select Set up.
    Original source Report a problem
  • Oct 16, 2025
    • Parsed from source:
      Oct 16, 2025
    • Detected by Releasebot:
      Oct 28, 2025

    Docs Collections by Cloudflare

    Increased HTTP header size limit to 128 KB

    Cloudflare expands header limits to 128 KB for both requests and responses, reducing 413 and 520 errors and enabling broader use cases. Larger headers support more cookies, bigger CSP headers, and advanced Cloudflare Workers scenarios with ease.

    We're excited to announce a significant increase in the maximum header size supported by Cloudflare's Content Delivery Network (CDN). Cloudflare now supports up to 128 KB for both request and response headers.

    Previously, customers were limited to a total of 32 KB for request or response headers, with a maximum of 16 KB per individual header. Larger headers could cause requests to fail with HTTP 413 (Request Header Fields Too Large) errors.

    What's new?

    • Support for large headers: You can now utilize much larger headers, whether as a single large header up to 128 KB or split over multiple headers.
    • Reduces 413 and 520 HTTP errors: This change drastically reduces the likelihood of customers encountering HTTP 413 errors from large request headers or HTTP 520 errors caused by oversized response headers, improving the overall reliability of your web applications.
    • Enhanced functionality: This is especially beneficial for applications that rely on:
      • A large number of cookies.
      • Large Content-Security-Policy (CSP) response headers.
      • Advanced use cases with Cloudflare Workers that generate large response headers.

    This enhancement improves compatibility with Cloudflare's CDN, enabling more use cases that previously failed due to header size limits.

    To learn more and get started, refer to the Cloudflare Fundamentals documentation.

    Original source Report a problem
  • Oct 14, 2025
    • Parsed from source:
      Oct 14, 2025
    • Detected by Releasebot:
      Oct 28, 2025

    Docs Collections by Cloudflare

    Single sign-on now manageable in the user experience

    Birthday Week

    During Birthday Week, we announced that single sign-on (SSO) is available for free to everyone who signs in with a custom email domain and maintains a compatible identity provider. SSO minimizes user friction around login and provides the strongest security posture available. At the time, this could only be configured using the API.

    Today, we are launching a new user experience which allows users to manage their SSO configuration from within the Cloudflare dashboard. You can access this by going to Manage account > Members > Settings .

    For more information

    • Cloudflare dashboard SSO
    Original source Report a problem
  • Oct 7, 2025
    • Parsed from source:
      Oct 7, 2025
    • Detected by Releasebot:
      Oct 28, 2025

    Docs Collections by Cloudflare

    Automated reminders for backup codes

    Cloudflare rolls out email and in‑product reminders prompting users to download backup codes for 2FA, helping recovery if credentials are lost. It also highlights sign‑in security best practices, backup code storage, and options like SSO and password hygiene.

    The most common reason users contact Cloudflare support is lost two-factor authentication (2FA) credentials. Cloudflare supports both app-based and hardware keys for 2FA, but you could lose access to your account if you lose these. Over the past few weeks, we have been rolling out email and in-product reminders that remind you to also download backup codes (sometimes called recovery keys) that can get you back into your account in the event you lose your 2FA credentials. Download your backup codes now by logging into Cloudflare, then navigating to Profile > Security & Authentication > Backup codes .

    Sign-in security best practices
    Cloudflare is critical infrastructure, and you should protect it as such. Please review the following best practices and make sure you are doing your part to secure your account.

    • Use a unique password for every website, including Cloudflare, and store it in a password manager like 1Password or Keeper. These services are cross-platform and simplify the process of managing secure passwords.
    • Use 2FA to make it harder for an attacker to get into your account in the event your password is leaked
    • Store your backup codes securely. A password manager is the best place since it keeps the backup codes encrypted, but you can also print them and put them somewhere safe in your home.
    • If you use an app to manage your 2FA keys, enable cloud backup, so that you don't lose your keys in the event you lose your phone.
    • If you use a custom email domain to sign in, configure SSO .
    • If you use a public email domain like Gmail or Hotmail, you can also use social login with Apple, GitHub, or Google to sign in.
    • If you manage a Cloudflare account for work:
      • Have at least two administrators in case one of them unexpectedly leaves your company
      • Use SCIM to automate permissions management for members in your Cloudflare account
    Original source Report a problem
  • Oct 2, 2025
    • Parsed from source:
      Oct 2, 2025
    • Detected by Releasebot:
      Oct 28, 2025

    Docs Collections by Cloudflare

    Fine-grained Permissioning for Access for Apps, IdPs, & Targets now in Public Beta

    Cloudflare rolls out fine grained RBAC for Access Applications, Identity Providers and Targets in public beta, letting admins grant permissions at the individual resource level. The beta requires a read‑only account scope to view resources, with plans to lift this later.

    What's New

    • Access Applications: Grant admin permissions to specific Access Applications.
    • Identity Providers: Grant admin permissions to individual Identity Providers.
    • Targets: Grant admin rights to specific Targets

    During the public beta, members must also be assigned an account-scoped, read only role to view resources in the dashboard. This restriction will be lifted in a future release.

    • Account Read Only plus a fine-grained permission for a specific App, IdP, or Target
    • Cloudflare Zero Trust Read Only plus fine-grained permission for a specific App, IdP, or Target

    For more info

    • Get started with Cloudflare Permissioning
    • Manage Member Permissioning via the UI & API
    Original source Report a problem
  • Oct 1, 2025
    • Parsed from source:
      Oct 1, 2025
    • Detected by Releasebot:
      Oct 28, 2025

    Docs Collections by Cloudflare

    Return markdown

    Users can now specify that they want to retrieve Cloudflare documentation as markdown rather than the previous HTML default. This can significantly reduce token consumption when used alongside Large Language Model (LLM) tools.

    If you maintain your own site and want to adopt this practice using Cloudflare Workers for your own users you can follow the example here.

    Original source Report a problem

This is the end. You've seen all the release notes in this feed!

Related products