Poor user experience with 'Invite-only' 'Login required'

AI-generated summary

Multimastery reported a poor user experience when using ‘Invite-only’ combined with ‘Login required’ settings. The issue allowed users to complete the entire sign-up process, including email confirmation and profile setup, only to be blocked at the end because the site was invite-only. Moin suggested disabling the beta enable local logins via code setting or using the discourse_skip_email_verification plugin, though Multimastery dismissed the plugin due to security concerns regarding bot access (posts 7-8).

awesomerobot identified the root cause as a gap in the Discourse ID flow specific to the Free plan. On Free plans, Discourse ID serves as the authentication system, which operates independently of the site’s invite settings. Consequently, users could create a Discourse ID account but would hit a wall upon returning to the invite-only site. awesomerobot acknowledged the need to check for invite-only status before initiating the Discourse ID signup process.

pmusaraj subsequently merged a fix (PR #46409) that addresses this issue. The update introduces a clearer landing page for invite-only, login-required sites. This page warns users that they need an invitation before they begin the sign-up process, preventing wasted time. The fix was scheduled to roll out to all hosted sites within 24-48 hours.

I’ve been testing with the ‘Invite-only’ ‘Login required’ settings enabled and the flow doesn’t make sense to me at all. What I don’t like is that it takes someone through the entire sign-up process, email confirmation and all, prompting them to fill out their profile and all - and then at the end it hits them with invite-only. That’s a total waste of someone’s time, a bad user experience, and makes no sense at all.

I went back & forth with the ‘AI Assistant’, but it’s just going around in circles agreeinf that it’s a bad user experience, but it’s still stumped for any solution.

So if an actual person can chime in on this issue, I’d appreciate it.

There is an upcoming change, enable local logins via code. It’s currently in beta status, so it is enabled by default. Did you try disabling that? There is a chance the experience is better with it disabled.

I have a similar problem on my forum, where signing up with an invite code doesn’t work because email isn’t sent to the user at all.

I don’t see exactly what you’re referring to. But I do see “Enable local logins via email”, and no, I don’t have that checked.

The closest thing I see that sounds like what your referring to is where it says ‘Invite only’ (which I have the box checked), and under it, it says ‘Invite code’ (which I left empty).

I think that you might look into this:

Then install and enable this plugin, for avoid unnecessary friction (just keep in mind that bots can get into your community easily):

Are you on the discourse.org Free plan by any chance? this seems like a gap in our Discourse ID flow for logging in on Free sites.

Typically when “invite only” is enabled, registration is disabled entirely so you can’t reach that account creation flow.

But our Free plan requires Discourse ID as its auth system, which is a separate centralized Discourse registration system that isn’t directly controlled by your site.

So what happens is someone creates a Discourse ID, then that account gets sent back to log in to your site. Without invite-only this is somewhat invisible to the user, but when invite-only is enabled they can successfully create a new Discourse ID account, and hit a wall when directed back to your site.

We should check for invite-only before sending people to the Discourse ID signup process so we can prevent this sort of annoyance.

Yes, I’m on the free plan.

I’m sorry but I just don’t see how this will solve the sign-up flow that I’m referring to. Plus, why would I want to install something where bots can easily get into??

Yes, I’m on the free plan.

Understood, you’ll have to hold tight until our workweek starts and we have a chance to consider and prioritize a potential fix.

I have just merged a fix for this: UX: Show invitation requirements before external login - Pull Request #46409 - discourse/discourse - GitHub

On invite-only login-required sites we will now show a clearer landing page that instructs people to use invitation links. So, before they embark on the sign-up process, they are warned that they need an invite.

The fix should land on all sites on our hosting over the next 24-48 hours.