Skip to content

Conversation

@wangsijie
Copy link
Contributor

Summary

  • Add info boxes to explain the difference between logto-verification-id (header) and newIdentifierVerificationRecordId (body)
  • Add inline comments and descriptive placeholder names in code examples
  • Applied to both "Update or link new email" and "Link a new social connection" sections

Users frequently confuse these two verification record IDs when linking identifiers. This change makes the documentation clearer by explicitly explaining:

  • Header ID: Proves user identity (from password or existing email/phone verification)
  • Body ID: Proves ownership of the new identifier being linked

Test plan

  • Preview the docs and verify the info boxes render correctly
  • Verify the code examples are clear and properly formatted

Add info boxes and code comments to distinguish between:
- logto-verification-id (header): proves user identity
- newIdentifierVerificationRecordId (body): proves ownership of new identifier

This helps users understand which verification ID to use where when
linking email, phone, or social connections.
@cloudflare-workers-and-pages
Copy link

Deploying logto-docs-tutorials with  Cloudflare Pages  Cloudflare Pages

Latest commit: 0854bb2
Status: ✅  Deploy successful!
Preview URL: https://d7d7f0ce.logto-docs-tutorials.pages.dev
Branch Preview URL: https://docs-clarify-verification-re.logto-docs-tutorials.pages.dev

View logs

@cloudflare-workers-and-pages
Copy link

Deploying logto-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 0854bb2
Status: ✅  Deploy successful!
Preview URL: https://9097fa8d.logto-docs.pages.dev
Branch Preview URL: https://docs-clarify-verification-re.logto-docs.pages.dev

View logs

@wangsijie wangsijie enabled auto-merge (squash) January 12, 2026 02:33
@wangsijie wangsijie merged commit 4525701 into master Jan 12, 2026
19 checks passed
@wangsijie wangsijie deleted the docs/clarify-verification-record-ids branch January 12, 2026 02:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants