A site is not only pages — it also gets mail on its own domain. The moment a site is published, it has a mailbox, and you can add as many more as you need. Nothing to install: the mailboxes are opened in the browser, from the same place you manage the site.

Where mail lives

Open the site and choose Mailboxes. The summary at the top shows how many mailboxes exist, how many API keys are active for this domain, and the domain itself — click it to copy the @domain part, which is what people usually need when they are typing an address by hand.

The support@ mailbox is created with the site and is the default destination for site notifications and form submissions. It is worth keeping even if you add personal addresses.

Create a mailbox

  1. Press New mailbox.
  2. Enter the local part — the piece before the @. Letters, digits, dot and dash only.
  3. Set a password of at least eight characters. It is what you will use to open the mailbox.
  4. Press Create. The address appears in the list straight away and can receive mail immediately.

Day-to-day

  • Open mailbox — reads and writes mail in the browser, no client to configure.
  • Copy address — puts the full address on the clipboard.
  • Reset password — sets a new one; use it when somebody forgets theirs or leaves.
  • Delete — removes the mailbox and everything in it, so the confirmation says so plainly. You cannot delete the mailbox you are signed in with.

Once there are more than a few, a search box appears above the list — type any part of an address to filter.

Signing in

Managing mailboxes needs a signed-in session for the site, because these are real accounts with real passwords. Without it you can still see the site's own mailbox, but creating, opening or deleting requires signing in first — the prompt appears in place of the list.

Sending from the site

The same domain is used for the mail your site sends. Under Emails you keep the site's transactional and marketing templates — a welcome message, an order confirmation, a password reset — and edit any of them in the email builder by clicking it.

Each template has a Send / API panel with a live preview, the variables it accepts, and ready-made preview and send URLs you can copy — enough to trigger the email from a script or another system without writing an integration first.

A few practical notes

  • Use role addresses for anything shared — support@, hello@, billing@ — and personal ones only for people. Roles survive staff changes; personal addresses do not.
  • Give every mailbox its own password rather than sharing one. Resetting a single mailbox is then a one-minute job.
  • Before announcing a new address anywhere, send yourself a test to it and reply from it — that checks both directions in one go.