Multimastery reported a poor user experience on sites configured as “Invite-only” with “Login required,” where uninvited users are forced through the full sign-up and profile creation process only to be blocked at the end. After failing to find a solution with an AI assistant, they sought human support.
Moin suggested testing the enable local logins via code setting, noting a similar issue where invite codes failed due to email delivery problems. satonotdead recommended a plugin to skip email verification to reduce friction, though Multimastery rejected it due to bot security concerns and confusion about the suggested settings.
The root cause was identified by awesomerobot as a specific gap in the Discourse ID flow for Free plan sites. Unlike standard sites where “invite only” disables registration, Free plan sites use the centralized Discourse ID system. This allows users to create a Discourse ID successfully, only to be blocked when redirected back to the invite-only site. Multimastery confirmed they were on the Free plan.
pmusaraj announced a merged fix that modifies the landing page for invite-only, login-required sites. Instead of allowing users to start the sign-up process, the site now displays a clear message instructing them to use an invitation link first. This change prevents the wasted effort of account creation. The update was scheduled to roll out on hosted sites within 24–48 hours, a resolution Multimastery approved of in the final reply.
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??
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.