# Community emails & signup notifications

> The emails your community sends — confirmation codes, resets, approvals — now carry your name, logo, and reply-to address, and you get an email when someone joins.

Source: https://knowledge.estage.com/community/email-branding/
Part of the ESTAGE knowledge base (https://knowledge.estage.com). Full corpus: https://knowledge.estage.com/llms-full.txt

---
Every mail your members used to get from a community — the signup confirmation code, the resend,
password reset, an approval or a decline, licence notices — arrived signed **ESTAGE** and pointed
at Estage support. Your members had never heard of Estage, and a reply landed with us instead of
with you.

**Those emails now wear your brand.**

## What changes

- **Your name beside the sender**, so the mail is recognisable in the inbox before the subject line
  is read.
- **Your logo in the message** — an image or a text logo, whichever you set.
- **Your support address as Reply-To**, so replies reach the person who can actually answer them.
- **No "ESTAGE" left in the body** — the sign-off is the community's.

Set it in your community's **Settings → General**: the **Support / reply-to email** field and the
**Email branding** block (logo image or logo text).

:::note
Nothing to verify, no DNS setup. The sending address stays ours — only the display name, the logo,
and the Reply-To change. (To send your *own* marketing email from your own authenticated domain,
that's [Email sending](/email/).)
:::

## You get told when someone joins

When a signup is **confirmed**, the project owner gets an email about it: name, email, phone, when
it happened, which community, and whether this is a brand-new Estage account or an existing user
joining you.

- It's sent when the **code is confirmed**, not when the form is submitted — so you're reading
  about people who actually arrived.
- If your community **approves members manually**, the mail says the person is waiting on you — in
  the subject, in the details, and at the end — and points you at the **Members** tab where you
  approve them. If they're already in, it says that instead.
- It carries the community's logo, name, and colours too.
- Running several communities? The sender carries the **project's name**, so you can tell them
  apart in the inbox list.

## Fallbacks

- **No support address set?** Genesis falls back sensibly: your project's
  [Business Details](/project-settings/business-details/) address first, then your account email.
- **Name:** community name → registered business name → project name.
- A support field containing something that **isn't an email** (a link, a whole paragraph — it
  happens) is simply ignored. Previously that quietly broke signups, code resends, and password
  resets for that community entirely.