<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Portal Best Practices For Communicating With External Users</title><link>https://community.appian.com/discussions/f/portals/38943/portal-best-practices-for-communicating-with-external-users</link><description>Hi, 
 I&amp;#39;m exploring the use of Appian Portals to allow external users to submit applications without requiring a login. One challenge I&amp;#39;m facing is figuring out the best way to communicate back to those users after they’ve submitted the form to make edits</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Portal Best Practices For Communicating With External Users</title><link>https://community.appian.com/thread/147292?ContentTypeID=1</link><pubDate>Thu, 17 Apr 2025 01:06:27 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6509e4bb-be45-4a53-a184-c93767bd9aec</guid><dc:creator>Mathieu Drouin</dc:creator><description>&lt;p&gt;I would personally go with the magic link pattern. Enter your email, you get a validation code sent to your email which you enter and view info related to your profile. You&amp;#39;ll have to store the session in a local variable and ensure that you manage everything within one page to ensure you don&amp;#39;t lose the context.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>