---
description: Understand Studio's Edge integration, public feature gates, newsletter activation, comment targets, and mail delivery.
---

# Edge & Mail

ZeroPress Edge provides runtime APIs for the public site's comments, forms,
and newsletters. Studio manages their data through its configured Edge
bindings. The public Edge Worker remains a separate deployment.

## Three Availability Layers

| Layer | Controls |
| --- | --- |
| Studio integration | Whether Studio uses the connected Edge database and KV |
| Public Edge Worker configuration | Whether public feature APIs are enabled and permitted to serve requests |
| Feature data | Whether a particular target, form, or newsletter list accepts the requested action |

Disabling Studio integration does not stop the public Worker. Likewise,
configured bindings alone do not mean public submissions are open. Review
Studio's Dashboard service readiness and the feature's runtime settings.

Keep Studio and the public Edge Worker connected to the intended matching
resources. A ready Studio database does not imply the Edge schema is ready.
Use [Operations](../../operations/maintenance-and-recovery/index.md#edge-database-lifecycle)
when Edge needs installation, upgrade, adoption, or reconciliation.

## Comments and Target Synchronization

When integration is enabled, Studio records changes for projection to Edge
comment targets. Content writes and their projection-outbox entries commit
together in Studio. Processing the outbox updates Edge separately.

This boundary lets a committed document remain available while target
synchronization is pending. Preview Data preparation checks that required
targets are consistent before exporting their public comment information.

The Comments All tab excludes Spam and Trash. Status tabs have their own URLs;
pending-moderation links open Pending directly. Restore returns trashed
comments to Pending, and permanent deletion is available from Trash.

## Forms and Newsletters

Public forms need both an enabled runtime and an available form definition.
Newsletter subscriptions additionally require an active list. A freshly
initialized Edge database seeds the default newsletter list as **archived**,
so new public subscriptions remain closed until it is activated.

Use **Newsletters → Subscription settings** to open or close signups, and
check the public Worker's newsletter gate as well. Enabling the Worker alone
does not activate the list. Review field definitions and confirmation delivery
before opening subscriptions.

Form submissions and newsletter subscriber records remain runtime data in
Edge. They are not part of the public site's Preview Data export.

## Mail Delivery

Studio supports Resend and Cloudflare mail delivery, with delivery disabled by
default. Configure the provider, approved sender, and credentials in
**Site Settings → Mail delivery**.

Credential verification checks the provider credential. A separate, confirmed
test email uses the saved sender and verifies that the provider accepts a
message. Acceptance is not a guarantee that the recipient's inbox delivered it.

Mail work uses the configured Queue producer and consumer. Their names must
identify the same Queue. Provider settings, Queue connectivity, and compatible
Edge data all affect whether newsletter and form messages can be processed.

Saved mail credentials are encrypted under `STUDIO_AUTH_SECRET`; keep that
Secret with the database or replace the credentials after changing it.

## Maintenance

Before Edge database work, pause the public Edge Worker with
`EDGE_MAINTENANCE_MODE=true` and consider pending mail work. Studio's
maintenance mode cannot pause requests or Queue production from another Worker.

Follow the [Edge lifecycle workflow](../../operations/maintenance-and-recovery/index.md#edge-database-lifecycle)
and preserve a separate Edge backup. Enabling Studio integration afterward is
an explicit setting change, not an automatic effect of database repair.