Authentication: Email Template - APP NAME

General
1

In the Firebase Hosting authentication email template, the App Name is showing the project ID instead. I’ve updated the app name in all possible locations, but the template still doesn’t reflect my App Name. Also, the email body content seems to be non-editable. What can I do to fix this?

2

Hi there — welcome to the community!

When customizing Firebase Authentication email templates, the App name that appears in those emails comes from your Firebase project settings, not the codebase itself.

Here’s how to make sure your project’s display name is showing up correctly:

  1. Check the project name in Firebase Console

    • Go to Firebase Console → Project Settings (:gear:) → General tab.

    • Under “Your project”, update the Public-facing name.

    • This is the name Firebase uses in your verification and password reset emails.

  2. Edit the email template directly (optional)

    • Navigate to Authentication → Templates.

    • You can manually adjust the text and insert variables like ${APP_NAME} or hardcode a custom app name if you want more control.

  3. Test using the Preview / Send Test Email

    • Use the built-in Preview or Send test email button to verify the changes.

    • Sometimes caching delays the display, so give it a few minutes after saving before testing again.

If you’re using multi-environment setups (e.g., dev / staging / production), you’ll want to confirm that the correct project is selected in the top dropdown — otherwise, you might be editing the wrong environment’s template. This is very important to a clean environment. Here is a sample of how I set up a recent project:

/
├── .env
├── README.md
├── apphosting.yaml
├── components.json
├── next.config.ts
├── package.json
├── tailwind.config.ts
├── tsconfig.json
│
└── src/
├── ai/
│ ├── dev.ts
│ ├── genkit.ts
│ └── flows/
│ ├── generate-faction-lore.ts
│ └── smart-golem-upgrades.ts
│
├── app/
│ ├── actions.ts
│ ├── globals.css
│ ├── layout.tsx
│ ├── page.tsx
│ ├── dashboard/
│ │ └── page.tsx
│ ├── game/
│ │ └── page.tsx
│ └── mint-lab/
│ └── page.tsx
│
├── components/
│ ├── dashboard/
│ │ ├── dashboard.tsx
│ │ ├── event-feed.tsx
│ │ ├── faction-hub.tsx
│ │ ├── golem-forge.tsx
│ │ └── stats-overview.tsx
│ │
│ ├── game/
│ │ └── game-header.tsx
│ │
│ ├── landing/
│ │ └── coliseum-entry.tsx
│ │
│ └── ui/
│ ├── accordion.tsx
│ ├── alert-dialog.tsx
│ ├── alert.tsx
│ ├── avatar.tsx
│ ├── badge.tsx
│ ├── button.tsx
│ ├── calendar.tsx
│ ├── card.tsx
│ ├── carousel.tsx
│ ├── chart.tsx
│ ├── checkbox.tsx
│ ├── collapsible.tsx
│ ├── dialog.tsx
│ ├── dropdown-menu.tsx
│ ├── form.tsx
│ ├── input.tsx
│ ├── label.tsx
│ ├── menubar.tsx
│ ├── popover.tsx
│ ├── progress.tsx
│ ├── radio-group.tsx
│ ├── scroll-area.tsx
│ ├── select.tsx
│ ├── separator.tsx
│ ├── sheet.tsx
│ ├── sidebar.tsx
│ ├── skeleton.tsx
│ ├── slider.tsx
│ ├── switch.tsx
│ ├── table.tsx
│ ├── tabs.tsx
│ ├── textarea.tsx
│ ├── toast.tsx
│ └── toaster.tsx
│
├── hooks/
│ ├── use-mobile.tsx
│ └── use-toast.ts
│
└── lib/
├── mock-data.ts
├── placeholder-images.json
├── placeholder-images.ts
├── types.ts
├── utils.ts
└── wallet.ts

Each one of the files in this project need to be in line with Firebase Rules. I advise that you take 72 hrs. to read the Documentation, and 48 hrs. to redesign your application using Figma. If you don’t have Logs you need to set this up, and you should have a solid Git Repository fully fleshed out and matching your projects, Tree. See if this helps get you moving in the right direction and back on schedule

Everything you see here was created inside Firebase. This is how you can train the Gemini AI bot to assist you in building the application you want. If you are using Snippets from another AI, you can encounter some mismatch. Another easy mistake is to not read the AI that generated the snippets full response. The outcome is using example code, where your Firebase is using accepted coding practices for its design, not as a matter of Coding Practices and Procedures that an organization will adopt or use for what they are doing, if that makes sense.

3

Thank you for your help and support. I don’t have a “Public-facing name” option — only an “App nickname.” I’ve changed it multiple times and tried several times, but it’s still not working.

4

Sorry, I just realized the issue. In Authentication, I had only activated the Email/Password sign-in method. After enabling Google sign-in, I can now see the Public-facing name option. Thanks!

1 Like