# Email Customization

Buzzy allows administrators to customize the emails sent from their deployment, including branding, sender information, and content. This feature provides a user-friendly interface to configure email settings without modifying server configuration files.

## Prerequisites

Before you can customize emails, you need:

1. **Your own Buzzy Deployment** - Email customization is only available for self-hosted deployments
2. **Secure SMTP configured** - Set up email delivery following the [Email Deliverability Guide](/working-with-buzzy/buzzy-deployment-and-app-stores/email-deliverability-guide.md)

## Accessing Email Customization Settings

1. Log in to your Buzzy deployment as an administrator
2. Navigate to **Settings**
3. Expand the **Email Customization** section

## Configuration Options

### App Name (in emails)

Override the application name that appears in email communications. This allows you to brand emails with your organization's name rather than the default deployment name.

**Example**: If your deployment is named "Acme Corp Buzzy" but you want emails to simply say "Acme Portal", enter "Acme Portal" here.

### Reply-To Email

Set the email address that recipients will reply to when they respond to Buzzy emails. This is useful when you want replies to go to a support inbox rather than a no-reply address.

**Example**: `support@yourcompany.com`

### Reply Name

Set the display name associated with the Reply-To email address. This name appears in email clients alongside the reply address.

**Example**: "Acme Support Team"

### From Email

Customize the display "From" address shown in emails. This changes only the display address that recipients see - the actual SMTP/MAIL\_URL configuration remains unchanged for delivery purposes.

**Example**: `notifications@yourcompany.com`

{% hint style="info" %}
The From Email setting only changes the display address. Your SMTP configuration (MAIL\_URL) determines the actual sending server and authentication.
{% endhint %}

### Custom Logo

Upload a custom logo to appear in email communications instead of the default Buzzy logo.

**Requirements**:

* Format: PNG or JPG
* Width: 150px wide (recommended)
* Storage: Uploaded logos are stored in your app's S3 bucket

Click **Upload Logo** to select and upload your logo file.

### Before CTA (Markdown)

Add optional content that appears before the main call-to-action button in emails (such as login links). This field supports Markdown formatting, allowing you to include:

* Custom welcome messages
* Important notices or disclaimers
* Links to additional resources
* Formatted text with bold, italic, or lists

**Example**:

```markdown
Welcome to our platform! If you have any questions, please contact [support@yourcompany.com](mailto:support@yourcompany.com).
```

## Troubleshooting

### Logo not displaying in emails

* Verify the image is in PNG or JPG format
* Check that the image uploaded successfully to S3
* Ensure your S3 bucket permissions allow public read access for email assets

### Changes not reflected in emails

* Email customization changes take effect immediately for new emails
* Previously queued or cached emails may still show old settings
* Clear any email preview caches if testing

## Related Documentation

* [Email Deliverability Guide](/working-with-buzzy/buzzy-deployment-and-app-stores/email-deliverability-guide.md) - Configure SMTP and improve email delivery
* [Setting up your custom Buzzy app](/working-with-buzzy/buzzy-deployment-and-app-stores/setting-up-your-custom-buzzy-app.md) - General deployment configuration
* [Buzzy Settings](/advanced-deployment-settings/installation/buzzy-settings.md) - Server-level configuration options


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.buzzy.buzz/working-with-buzzy/buzzy-deployment-and-app-stores/email-customization.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.