Skip to content

[Support Feedback] Improve account, auth, and domain docs (Fundamentals)#28991

Open
dmmulroy wants to merge 3 commits intocloudflare:productionfrom
dmmulroy:support-macros/fundamentals
Open

[Support Feedback] Improve account, auth, and domain docs (Fundamentals)#28991
dmmulroy wants to merge 3 commits intocloudflare:productionfrom
dmmulroy:support-macros/fundamentals

Conversation

@dmmulroy
Copy link

Summary

Improves documentation for high-volume support topics in Fundamentals, based on an audit of active support macros. These are the responses agents send most frequently — gaps here mean customers cannot self-serve.

Changes

  • 2FA recovery: Add self-service recovery steps, backup code location hints, and verification options
  • Email MFA: Document email-based MFA enrollment and troubleshooting
  • Password reset & login: Clarify Apple ID/social login limitations and recovery paths
  • Account security: Add compromised-account response checklist
  • Account deletion: Document prerequisites and data retention
  • Super Admin transfer: Add step-by-step swap procedure
  • Domain management: Expand move-domain checklist and auto-removal triggers
  • Compliance docs: Clarify how to request compliance documentation
  • Member management: Improve role and access documentation
  • Dashboard SSO: Add SSO testing guidance

Context

These changes are driven by recurring support cases. If you want to see the underlying support data (macro frequency, case volume by topic), reach out to @dmmulroy internally.

@dmmulroy dmmulroy force-pushed the support-macros/fundamentals branch from 1970b4e to a0fb0b1 Compare March 17, 2026 15:26
import { Render } from "~/components";

If you observe suspicious activity within your Cloudflare account, secure your account with these steps.
If you observe suspicious activity within your Cloudflare account, secure your account immediately. At a minimum, complete these actions as quickly as possible:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Listing out the items right before each step that is currently a header is redundant. I would remove the ordered list.

2. If needed, remove the previous Super Administrator.

Then, if needed, remove the previous Super Administrator.
## Swap Super Administrator email addresses
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Swap" may not be as clear to users. We should use "Change" or "Reassign"


If you cannot access the email address associated with the Super Administrator role:

1. **Recover the email account** — contact your email provider to regain access to the mailbox, or set up email forwarding from the old address to one you control.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The items in this ordered list should begin with capital letters if they're going to be full sentences.

If you miss this step, Cloudflare will import your proxied DNS records, which might cause your domain to experience a [1000 error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/).


1. **Remove DNSSEC configurations** — [disable DNSSEC](/dns/dnssec/) on the domain before moving it. DNSSEC records at the registrar will prevent the domain from activating in the new account.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should live under a header titled something like "Domain transfer checklist" because it has multiple steps. Warning messages are usually a sentence or two, not a list of steps.


1. **Moved** — Cloudflare detects that nameservers no longer point to Cloudflare and marks the domain as **Moved**. An email notification is sent to the account owner.
2. **Deleted** — For Free zones, Cloudflare automatically transitions the domain from Moved to Deleted after 7 days. At this stage, the domain can still be re-added.
3. **Purged** — 7 days after being marked Deleted, the zone is permanently purged. Zone settings are not preserved.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because this is a full sentence, it should begin with "Seven" instead of the number.

- If you are using a Cloudflare [CNAME setup](/dns/zone-setups/partial-setup/), [update your DNS records](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records) at your DNS provider to point to your website IPs or hostnames instead of Cloudflare.
- [Delete payment information](/billing/update-billing-info/#delete-your-current-payment-method)
- (*Optional*) [Download a copy of your invoices](/billing/invoices/#download-invoice). Once deleted, the invoices will no longer be accessible and cannot be re-sent to you.
Before Cloudflare can cancel your account and delete your personal information, complete the following steps for each domain associated with your Cloudflare account:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unsure why this was deleted and readded

## After deletion

- **Re-register with the same email** — you can sign up for a new Cloudflare account using the same email address. In most cases, the email is available for reuse immediately.
- **Re-invitation to other accounts** — if you were a member of other Cloudflare accounts or organizations, the account owner will need to re-invite you after you create a new account.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The first list items is confusing. It reads as though we're telling using to re-register with the same email they just deleted. This section can use some revision.

* **Different Cloudflare account email as Apple ID**: This option creates a new Cloudflare account. If you want to log in to an existing account, [change your email address](/fundamentals/user-profiles/change-password-or-email/) to match the one used for your Apple ID.

If you chose to share your email when creating a Cloudflare account with Apple ID and want to set a password and obtain an API key, go to the [Cloudflare dashboard](https://dash.cloudflare.com/login) login page and select **Forgot your password?** to trigger a password reset email.
##### Shared email (not hidden)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't typically use an H5. This should be revised

## Troubleshoot MFA

Cloudflare emails are sometimes flagged as spam by the recipient's email service. If you are expecting an authentication token, you should check the spam folder for any Cloudflare emails and configure a filter to allow Cloudflare emails from *[no-reply@notify.cloudflare.com](mailto:no-reply@notify.cloudflare.com)*\_**.**\_
### When does email MFA trigger?
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This heading is not clear and ideally shouldn't leave with a question

Email MFA challenges a login when the client IP address is not recognized for that account. This means you may be prompted for a code when logging in from a new network, device, or location.

If you still do not receive an email after ensuring your email service is not flagging Cloudflare, contact [Cloudflare Support](/support/contacting-cloudflare-support/).
### Not receiving the one-time code email
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would revise this based on the section above

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants