<p>It's been quite long time ago&nbsp;when I touched Community last time but if I remember&nbsp;correctly users are synced to Community via Http module.</p> <p>So here is a workflow:</p> <p>a) Http module ("EPiServer.Common.Web.Authorization.IntegrationHttpModule") is added to the list of modules</p> <pre class="brush:xml;auto-links:false;toolbar:false" contenteditable="false">&lt;add name="EPiServerCommonUserIntegration" type="EPiServer.Common.Web.Authorization.IntegrationHttpModule, EPiServer.Common.Web.Authorization" preCondition="managedHandler" /&gt;</pre> <p><br />b) this module verifies and makes sure that eventually there will be a record in Community data structures for the current user</p> <p>c)&nbsp;there is possibility to configure which users get synced based on their roles:</p> <pre class="brush:xml;auto-links:false;toolbar:false" contenteditable="false">&lt;episerver.common&gt; &lt;integration&gt; &lt;rolesToSynchronize&gt; &lt;add name="*" /&gt; &lt;/rolesToSynchronize&gt; &lt;rolesToTransfer&gt; &lt;add name="..." /&gt; &lt;/rolesToTransfer&gt; &lt;/integration&gt; </pre> <p></p> <p>d) Actual&nbsp;user creation happens in "EPiServer.Common.Web.Authorization.Integrator"</p> <p></p> <p>What we did back in time was to add another membership provider that knows how to authenticate users against 3rd party source, so whenever somebody was logging in - eventually our custom provider kicked in, we set users in special role that gets synced over to Community store.</p> <p>So generally speaking - if you are looking for&nbsp;another membership provider for the Community - I guess you need to add that membership provider to the list of providers (most probably you may need appropriate role provider as well) and play around sync process to get those users over to Community.</p>