Create changelog for recovery codes #25693
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
|
Preview URL: https://2e649ba8.preview.developers.cloudflare.com Files with changes (up to 15)
|
src/content/changelog/fundamentals/2025-10-07-recovery-codes.mdx
Outdated
Show resolved
Hide resolved
src/content/changelog/fundamentals/2025-10-07-recovery-codes.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: Patricia Santa Ana <[email protected]>
Co-authored-by: Patricia Santa Ana <[email protected]>
Comment on lines
+14
to
+22
| * 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](https://developers.cloudflare.com/cloudflare-one/applications/configure-apps/dash-sso-apps/). | ||
| * 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 |
Contributor
There was a problem hiding this comment.
Suggested change
| * 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](https://developers.cloudflare.com/cloudflare-one/applications/configure-apps/dash-sso-apps/). | |
| * 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 | |
| - 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 application to manage your 2FA keys, enable cloud backup, so that you do not lose your keys in the event you lose your phone. | |
| - If you use a custom email domain to sign in, [configure SSO](https://developers.cloudflare.com/cloudflare-one/applications/configure-apps/dash-sso-apps/). | |
| - 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. |
patriciasantaana
approved these changes
Oct 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds a changelog for our new recovery code reminders
Screenshots (optional)
Documentation checklist