Trying to help out in Customize registration form / hide or normalize username field - Support, I found that the Site Setting use_name_for_username_suggestions doesn’t seem to have any effect on my local signup form.
Tested on self-hosted 2026.3.0-latest.1 (41f62aab8e).
AskBot believes it definitely should work for SSO / OAuth2 account creation, but it can’t solidly confirm that it should function as an auto-suggest on the regular signup form.
I’m wondering if I have the wrong expectation for this setting – or if I’m right and a bug has been introduced somewhere, possibly in the fixes for topics like Offering blank username suggestions rather than ‘UserN’ at signup or “use email for username and name suggestions”.
Can anyone confirm whether this setting does something on your local signup form?
AskBot's explanation:
Based on what I was able to verify, use_name_for_username_suggestions is definitely used in external-auth account creation flows such as SSO / OAuth2 / DiscourseConnect. The setting context shows Discourse includes the user’s name as an input when resolving a suggested username in those paths:
/lib/auth/result.rb/app/models/discourse_connect.rb
I also found evidence that Discourse has username autocomplete/suggestion behavior in the normal signup form, so this feature does not appear to be SSO-only in concept. However, I could not find a current Meta source that conclusively proves the plain local signup form is wired to this specific site setting in all cases.
So the safest summary is:
- Confirmed:
use_name_for_username_suggestionsaffects SSO / OAuth2 / external auth username suggestion. - Likely intended: it also affects the standard local signup form username suggestion/autocomplete behavior.
- Not conclusively verified from Meta sources alone: whether the current local signup form always uses this exact setting.