Multimastery reports a poor user experience when using Discourse’s “Invite-only” and “Login required” settings, particularly on the Free plan. Users are guided through a full sign-up process—including email confirmation and profile completion—only to be blocked at the end because the site is invite-only. Moin suggests checking the enable local logins via code setting, though Multimastery clarifies they are using the “Invite only” checkbox and not seeing the specific setting mentioned.
satonotdead recommends installing the discourse_skip_email_verification plugin to reduce friction, but Multimastery dismisses this due to security concerns about bots entering the community.
The root cause is identified by awesomerobot: Discourse’s Free plan uses a centralized authentication system called Discourse ID, which operates independently of site-specific settings like “Invite-only.” Consequently, users can successfully create a Discourse ID account before being redirected back to the invite-only site, where they are then locked out. Standard Discourse installations typically disable the registration flow entirely when “Invite-only” is active, preventing this issue.
Multimastery confirms they are on the Free plan, and awesomerobot acknowledges the gap in the flow. They state that the team needs to prioritize a fix to check invite-only status before initiating the Discourse ID sign-up process, but no immediate solution is available.
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 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).
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.
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??