# Settings

Sender details, sending domains and workspace preferences. Delivery is managed by SendBeam.

## Settings Overview

Settings comes in two scopes, because they own different things. **Workspace settings** — reached from **Settings** in the sidebar — holds what belongs to one site: **General**, **Email & Domains**, **Team**, **API Keys** and **Webhooks**. **Account settings** — reached by clicking the account name at the foot of the sidebar — holds what every workspace shares: **Account** (your login and the workspaces the account owns), **Billing & Plans** and **Security**. Changes take effect immediately.

- **Delivery** — a status card on Email & Domains. Delivery is managed by SendBeam; there is nothing to configure.
- **Sending domains** — the domains your email may come from, verified with DNS records (Email & Domains).
- **Sender details** — the from-name and from-address pre-filled on new campaigns, and a test send (Email & Domains).
- **This workspace** — workspace name (admins can rename it there), slug, your role (Owner, Admin or Member) and the plan it inherits (Workspace settings → General).
- **Workspaces** — every workspace your login belongs to, and where you create new ones (Account settings → Account).
- **Your data** — a full export of the workspace, and self-serve deletion (Workspace settings → General).

> **Admin access required for most of it.** Sender details, sending domains, API keys, webhook endpoints, workspace creation, export and deletion are admin-only — over the API as well as in the app. Members can see the General tab and switch between the workspaces they belong to, but the admin-only sections show a note asking them to contact an admin instead of the controls.
> 

## Delivery

Every workspace sends through SendBeam's own delivery infrastructure. Messages are signed with DKIM for your verified domain, use an aligned return-path so SPF passes, and carry one-click unsubscribe headers. Bounces, complaints and unsubscribes flow back automatically: a hard bounce or a complaint changes the contact's status so the address is never sent to again.

Sending health is measured against clear complaint and bounce limits, described in the [Acceptable Use Policy](https://sendbeam.io/legal/acceptable-use). Cross the warning level and workspace admins are emailed; cross the pause level and sending stops for that workspace, and admins are emailed when that happens. The warning and pause emails quote your measured rate and the level it crossed, so you always know where you stand. A pause needs a meaningful sample, so a single complaint on a short list will not pause you. If sending is paused, fix the underlying list and [tell us](https://sendbeam.io/contact?s=support) and we will lift it.

### What a pause stops, and what it does not

A pause is a sending control, not a suspension of the account. You keep your data and your access
throughout, and the workspace tells you it is paused on the dashboard and in Workspace settings.

**While a workspace is paused, these do not go out:**

- Campaigns — both an immediate send and anything already queued or scheduled
- Automation steps that send email
- RSS-to-email sends
- The transactional API (/api/v1/transactional and /api/v1/send)
- Double opt-in confirmations, team invitations and test sends
- Contact-form and new-subscriber notifications to the workspace owner

**These are deliberately unaffected:**

- **Forms keep accepting submissions, and contacts keep arriving.** A pause stops mail leaving; it does not take the customer’s signup forms off their website. The subscriber is stored as usual — only the notification email to the owner is held back, so submissions can arrive unnoticed while a pause is on.
- **Scheduled campaigns still come due, and are cancelled rather than sent.** The queue processor refuses a paused workspace at the point of sending, so a campaign scheduled during a pause does not sit and wait for it to lift.
- **Platform notices from SendBeam still reach the workspace admins.** Anything sent with system:true bypasses the gate on purpose — including the notice that says the workspace has been paused. Without that exception the pause could not announce itself.
- **Signing in, the app, the API and exports all keep working.** A pause is a sending control, not a suspension. The customer can still read their data, fix their list and export everything.
- **Other workspaces on the same account are unaffected.** sending_paused is a column on the workspace, so pausing one site never stops another. An account-wide stop means pausing each workspace.

> **Watch your forms during a pause.** Signups and contact-form messages are still
> accepted and stored — only the notification email to you is held back. Check
> [Contacts](https://sendbeam.io/contacts) and your form submissions before you assume it has been quiet.
> 

Each plan also has an hourly sending ceiling as well as its monthly allowance; your plan's ceiling is shown under Billing. Campaign queues simply continue in the next hour; the single-send API returns `429` with a `Retry-After` header telling you when to try again.

There are no provider accounts or API keys to manage. Your monthly volume is set by your [plan](https://sendbeam.io/docs/admin/billing), and usage is shown on the Billing page.

## Sending Domains

### Why domain verification matters

Mailbox providers judge the domain after the @ in your from-address. Mail that is signed for that domain and comes from an authorised source lands in the inbox; mail that isn't is filtered or rejected. Verification proves to SendBeam, and to Gmail and Outlook, that you control the domain.

### Adding and verifying a domain

1. Open **Settings > Email & Domains** and add the domain (or subdomain) you want to send from.
2. Publish every CNAME record shown — a DKIM signing record, a return-path record and a provider record, three in total today — at your DNS provider, DNS-only rather than proxied. The card names the provider it detected for that domain. Where a provider has enabled Domain Connect for SendBeam it also offers **Connect with provider**, which takes you to that provider's own login to approve the same two records; SendBeam never receives a password or a token.
3. Click **Verify**, or simply wait: SendBeam re-checks the records automatically about every minute, and the status moves from **Add DNS records** through **Verifying** to **Verified**, usually within minutes.
4. Choose the from-address on that domain with **Set as default**. New campaigns use it by default.

Until a domain is verified, your workspace can send from a shared platform address. It is authenticated and works, but recipients see the shared domain rather than yours.

### DMARC

Publish a DMARC record for your domain (`_dmarc.yourdomain.com`, for example `v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com`). Because SendBeam aligns both DKIM and SPF to your domain, your mail passes DMARC, and the policy stops others forging your address.

## Sender Details

The **from-name** is what recipients see as the sender. Use a name they will recognise, such as your brand or "Sarah at Acme". The **from-address** must be the workspace's own shared platform address (`ws-@mail.sendbeam.io`; workspaces created earlier keep `@mail.sendbeam.io`) or an address on a sending domain *this workspace* has verified. SendBeam checks the address when you save it and again on every send; a domain verified in another workspace does not qualify. The from-name is cleaned of line breaks, quotes and angle brackets and kept to 80 characters. Every campaign, automation and API send uses the sender details saved here. Use **Send test email** on the same page to send a test to your own address from the current sender details.

## Account

The **General** tab of Workspace settings shows the workspace's name, slug, your role in it and the plan it inherits from the account. An admin can rename the workspace there at any time — type the new name and click **Save name**. The slug never changes, so links, exports and the delete confirmation keep working, and the sender name under Email & Domains is unaffected; the rename is recorded in the audit log. Your own name and email are under Account settings → **Account**. Set up or remove an authenticator app for sign-in under Account settings → **Security**; removing one requires a current code from the app.

Your own sign-in — your password, resetting it, and adding an authenticator app as a
second step — is covered on [Sign-in and security](https://sendbeam.io/docs/admin/security).

## Workspaces

One login can belong to several workspaces — one per site you run is the usual shape. Each workspace keeps its own contacts, lists, tags, segments, campaigns, templates, automations, forms, sending domains, API keys and team. What they share is the account's plan: contacts, monthly emails and seats are pooled across every workspace on the account and checked against one cap, while sending domains and live automations are allowed per workspace. A person who is an admin in one workspace can be a plain member in another.

Switch between workspaces from the switcher at the top of the sidebar, or from the **Workspaces** list under Account settings → Account. The workspace you are in is remembered on your login, so every tab and device follows the switch.

### Creating a workspace

Under **Account settings → Account → Workspaces**, name the new workspace (after the site, usually) and click **Create workspace**. You become its owner and are taken straight there. The new workspace shares your account's plan and limits from the start; only workspace admins can create workspaces.

How many workspaces an account may hold is a plan limit: Free 2, Starter 5, Pro and Business unlimited. The current count and allowance are shown under the form.

### Joining a workspace

Accept a team invitation with the email you already sign in with and the workspace is added to your login — no second account. Pick it from the switcher next time you sign in. Being removed from a workspace's team takes that workspace away from your login; your other workspaces are untouched. See [Team management](https://sendbeam.io/docs/admin/team).

## Your data

### Export

Admins can download everything the workspace owns as one JSON file from **Workspace settings → General → Your data**: contacts with their tags and lists, lists, tags, segments, templates, campaigns, automations with their steps, forms, sending domains and the team. Credentials, API keys, billing identifiers and per-message delivery logs are never included. Click **Download export**; the file is generated on request and downloads immediately.

### Deleting a workspace

The workspace owner can delete it from the same section by typing its slug to confirm and
clicking **Delete workspace**; other admins see a note saying who to ask. The
account's paid subscription, if any, is cancelled first — if that fails, nothing is
deleted and you are asked to cancel billing from Account settings → Billing or try again.

Access ends straight away: the workspace disappears from the switcher, its sending domains are
released along with any DNS records SendBeam added for them, team members are moved to another
workspace they belong to, and a login that belonged to no other workspace is closed. Nothing
inside it is destroyed for **14 days**, though. For that fortnight it sits in the
bin at the bottom of **Account settings → Workspaces**, where the person who
deleted it, the owner or an account admin can **Restore** it — contacts,
campaigns, automations, forms and history intact. The bin shows how many days each one has left.

After the 14 days it is purged and gone for good: contacts, campaigns, automations, forms, API
keys and delivery history are all removed. When it was the last workspace on the account, the
account and its billing customer are closed too. Take an export first if you might need the
data in a form you can read elsewhere.

**Retention.** Individual engagement events (each open and click) are kept for 180
days and contact-form submissions for 90 days. Send records — recipient, subject, delivery
status and first open and click — are kept for the life of the workspace, with the address
of a deleted contact replaced by an anonymous placeholder.

> **The window is the undo.** Restore it within the 14 days and everything comes
> back. Once it has been purged, nothing — not support, not a backup — brings it
> back, so take the export if there is any doubt.
> 

## Blueprints

A blueprint is a reusable starting point for the next site you set up: one workspace's
**custom fields, automations and email templates**, saved under a name that every
workspace on your account can then start from. It belongs to the account rather than to the
workspace it came from, so an agency sets one site up carefully and the next five begin where
that one finished.

What a blueprint deliberately does *not* carry is customer data and anything that is
proved per workspace: contacts, lists and sending domains are never captured. A domain is
verified against its own DNS records in the workspace that sends from it, and cannot be cloned.

**Saving one.** Under **Workspace settings → General → Blueprints**, give it a name and an optional description of what it is for, and click
**Save as blueprint**. The list below then shows it with what it holds — so
many fields, so many automations, so many templates.

**Applying one.** Pick it from the same panel and click **Apply to this workspace**, or choose it when you create a workspace, which is the better moment:
the destination is empty and there is nothing to reconcile. Applying it into a workspace that
is already running is allowed, and the page warns you when this one has live automations.

What happens when it is applied:

- A custom field whose key already exists here is **left alone**, never
  overwritten, and reported as skipped. Everything else is created.
- Automations arrive with the tags, lists and fields they need, created under their saved
  names if they are missing.
- Templates arrive with their images, copied into this workspace so the result does not
  depend on the workspace the blueprint came from still existing.

Saving and applying are admin-only, and deleting a blueprint never touches a workspace it was
already applied to — what it created is that workspace's own from the moment it lands.

## Troubleshooting

- **Campaign refuses to send with "Monthly email limit reached".** The account has used its plan's quota across all its workspaces. Upgrade on the Billing & Plans page, or wait for the reset at the start of next month.
- **"Sending health warning" email.** The workspace's complaint or bounce rate has reached the warning level; the email quotes the measured rate. Clean the list and send only to people who asked to hear from you before it reaches the pause line.
- **"Sending is paused".** The complaint or bounce rate exceeded the threshold. Review recent campaigns and list sources, then get in touch through the [contact form](https://sendbeam.io/contact) to have sending resumed.
- **"Hourly send limit reached" (API).** The plan's hourly ceiling is used up. Wait for the `Retry-After` period and retry; campaign queues resume by themselves.
- **Domain stuck on "Add DNS records".** Check the CNAME records match exactly, with no extra characters, and that they are not proxied through a CDN (on Cloudflare, set them to DNS-only). The table under the domain shows which records have been found. DNS changes can take up to an hour to be seen.
- **Emails going to spam.** Send from a verified domain rather than the shared address, publish DMARC, keep lists to people who opted in, and make unsubscribing easy.

---
Source: https://sendbeam.io/docs/admin/settings