Double Opt-in overkill 😅
Is there any guide that explains exactly when und how all double-opt-in (DOI) processes of FluentForms, FluentCRM & FluentCommunity work in conjunction with each other? I struggle to chose in which plugin I need to enable it in order to achieve the following:
A General Community (open for everyone after registration)
A1 - User signs-up for the general community using a FluentForm "A" (to notify admin)
A2 - User receives DOI mail and clicks "Confirm"
A3 - User will be redirected to a "Welcome" page (which includes links to the portal and other resources)
A4 - User receives a "Welcome" mail with further instructions about how to reset pw etc.
B Specific company space (open only for staff of a specific company)
B1 - User sign-up (FluentForm "B" where E-Mail need to end with @company.domain)
B2 - User receives DOI and confirms
B3 - User will be redirected to the company space
B4 - User receives "Welcome to company" mail with company-related infos
I have tried various combinations of enable/disable in FF & FC, since it's impossible to disable DOI in FluentCRM. All users in "A" or "B" still receive at least 2 DOI mails.
I wish there's a best-practice guide that explains exactly when to enable/disable DOI and where (FF or FC).
Having a bast practice guide would be higly appreciated here as well.
Having multiple options for connecting a FluentForm registrant through integration settings with FC and FCRM adds unnecessary confusion. When to use the FF integration? Or better to leave them unchecked and use an automation flow in FCRM only?
While my overall experience with all FluentPlugins has been excellent, but the registration process, integration setup, and DOI workflows make the entire admin experience feel overly complicated.