Require user's full name during sign up flow

[joshestein]

🧩 Summary

Multiple users have complained via bug reports that their names are not being shown on their FoAI certificates. During sign up, we only require an email. This leads to an empty space on the certificate where their name would be shown.

Users need to manually update their name via their profile settings. After they've done this, there is a delay where our webhooks sync data.

✅ Definition of done

We need a way to preemptively get users to submit their names. We could:

1. Change the sign up form to take a name input
2. Warn the users on the certificate page if there is no name
3. Prompt the users for their name at some point (after signing in)

I lean towards (1); this would require modifying bluedot-keycloak-theme, getBluedotKeycloakTheme.sh, Login.tsx and users.ts. This will only fix the issue for future sign ups. For currently signed up users we could consider some sort of in-app name capture - I don't feel strongly about this.

I also suggest that if users sign in with Google we automatically extract their name - there is no cost (aside from additional permissions).

📌 Notes / Designs

No response

[joshestein]

Data point from prod Postgres (2026-07-09) that bears on the "in-app name capture for existing users" question:

• 23,238 users have an empty name
• 11,078 of 15,645 self-serve course registrations (71%) link to a nameless user

So 71% of certificate-eligible registrations currently have no name to print on the certificate. Fixing the signup form only helps future accounts — an in-app prompt for existing users looks fairly important rather than optional.

Related: the empty names also cause Airtable validation warning spam from the fullName lookup on self-serve registrations — tracked separately in #2763. Correction: the warning spam turned out to be a regression from #2734 (writing name: '' on user creation), not a consequence of nameless users generally — see #2763 for the corrected diagnosis. The certificate stats above are unaffected.

[joshestein]

@anglilian I could use some product input here. Adding a 'name' input field to our Keycloak login is definitely feasible, but Will points out this might deter some users from signing in. What are your thoughts?

[anglilian]

I also suggest that if users sign in with Google we automatically extract their name - there is no cost (aside from additional permissions).

I definitely think we should implement this bit!

[anglilian]

We could add the name input field be on the page after they've signed in. @joshestein

Also, can we change the order of Google single sign on so people are more likely to use Google, then we don't have to ask them for their name.

[joshestein]

@anglilian

We could add the name input field be on the page after they've signed in

Which page are you referring to? I think this is the same as point (3) I listed in this issue description. Currently, we redirect to bluedot after login - I think if we then block waiting for a name input that needs some design to be unobtrusive.

[joshestein]

Putting Google first was already done over a year ago! But the change was never released.

bluedotimpact/bluedot-keycloak-theme#4

The PR introduced some changes that will remove headers for other pages though; I've created bluedotimpact/bluedot-keycloak-theme#7 to fix that. Let's wait for that to merge, then do a new release of the theme.

[anglilian]

We could implement a design like this, where the first and last name are optional, but if they don't fill it in they get this prompt to fill it in. Clickign continue should redirect them back to the web page they were last on. @joshestein

[joshestein]

I think the optional input fields on the sign up page, rather than redirecting to a new page, is the way to go 👍🏻