<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with phone number]]></title><description><![CDATA[A list of topics that have been tagged with phone number]]></description><link>https://fusionauth.io/community/forum/tags/phone number</link><generator>RSS for Node</generator><lastBuildDate>Mon, 08 Jun 2026 10:54:25 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/phone number.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[Email or phone number to login?]]></title><description><![CDATA[<p dir="auto">Yes. That’s how it currently works.</p>
<p dir="auto">We have on the roadmap a more flexible identity system but don't have a current timeline for implementation. Here's the tracking issue: <a href="https://github.com/FusionAuth/fusionauth-issues/issues/1" rel="nofollow ugc">https://github.com/FusionAuth/fusionauth-issues/issues/1</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/1221/email-or-phone-number-to-login</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/1221/email-or-phone-number-to-login</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>