New user onboarding emails: password-changed email sent first; neither email greets user by name or includes username / first-time login instructions

Aperta
  • Qualcosa non va?
#43,553 4 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
authentication, backend

Direzione di ricerca

Start by tracing the admin user creation flow and the code that sends the password changed and welcome emails; the issue does not name files or tests. Check how user name, username, workspace URL, and first login credentials are passed into each email, then review the relevant email tests. Done means new users receive clear, friendly login instructions with their name and username, without misleading password change wording.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

type: bug
Description

When an admin creates a new user (with name, email, and a default password), the email onboarding experience is confusing for a brand-new user. Two emails arrive, and between them the user is never told who they are, what their username is, or how to log in for the first time.

Email 1 — "Your password was changed by an admin" (arrives first)

Email 1 — password changed by an admin, temporary password redacted

Problems:

  1. Wrong framing for a brand-new account. The very first thing a new user learns about the product is that "your password was changed by an admin" — an alarming message about an account they've never used. This is really an "account created" email and should be worded like one.
  2. No greeting by name. It opens with a bare "Hi," even though the admin set the user's full name when creating the account.
  3. No username. The email gives a temporary password but never says what username (or that the email address) should be used to log in. The user has half the credentials.
Email 2 — welcome email

Email 2 — welcome email, workspace name and URL redacted

Problems:

  1. Generic marketing copy ("...try the best open source chat solution available today!") with no username, no temporary password, and no first-time login instructions.
  2. Also no name in the greeting.
Net result

A new user receives a scary-sounding password-change notice and a marketing email, and still has to ask the admin what their username is and where to log in. First-run onboarding via email effectively doesn't work.

Steps to reproduce
  1. As an admin, go to Administration → Users → New user.
  2. Fill in Name, Email, and a Password, and enable Send welcome email.
  3. Save the user.
  4. Check the new user's inbox: a "Your password was changed by an admin" email with a bare temporary password arrives first, followed by the generic welcome email.
Expected behavior

The email(s) sent when an admin creates a user should:

  • Greet the user by their name (it's already on the user record).
  • Tell the user their username (and/or that they can log in with their email address).
  • Make clear where to log in (the workspace URL), not just a Login button.
  • Be worded as an account created / welcome message rather than "your password was changed by an admin" — or at least use distinct, friendlier wording for newly created users versus actual password changes.
  • Ideally be a single coherent email containing name, username, workspace login URL, and either the temporary password or a set-your-own-password link, so the user can log in on the first try without asking the admin anything.
Actual behavior
  • The first email is a password-changed notice; the second is a generic marketing welcome.
  • Neither email uses the user's name ("Hi,").
  • Neither email states the username or how to log in for the first time.
Server Setup Information
  • Rocket.Chat Version: 8.9
Lingua principale
TypeScript
Stelle
46.5k
Fork
14.1k
Merge medio
1g 21h
PR unite (30g)
381

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di RocketChat/Rocket.Chat

Tutte le issue di RocketChat/Rocket.Chat

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.